CVE-2026-39961
Description
Aiven Operator allows you to provision and manage Aiven Services from your Kubernetes cluster. From 0.31.0 to before 0.37.0, a developer with create permission on ClickhouseUser CRDs in their own namespace can exfiltrate secrets from any other namespace — production database credentials, API keys, service tokens — with a single kubectl apply. The operator reads the victim's secret using its ClusterRole and writes the password into a new secret in the attacker's namespace. The operator acts as a confused deputy: its ServiceAccount has cluster-wide secret read/write (aiven-operator-role ClusterRole), and it trusts user-supplied namespace values in spec.connInfoSecretSource.namespace without validation. No admission webhook enforces this boundary — the ServiceUser webhook returns nil, and no ClickhouseUser webhook exists. This vulnerability is fixed in 0.37.0.
How to fix
- aiven aiven_operator0.37.0 or later
- github.com/aiven/aiven-operator0.37.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| aiven aiven_operator | 0.31.0 ≤ v < 0.37.0 | 0.37.0 |
| github.com/aiven/aiven-operatorGo | 0.31.0 ≤ v < 0.37.0 | 0.37.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.