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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-269",
"CWE-441"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/39xxx/CVE-2026-39961.json"
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:aiven:aiven_operator:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0.31.0"
},
{
"fixed": "0.37.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "032c9ba63257fdd2fddfb7f73f71830e371ff182"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v0.37.0",
"range": [
{
"fixed": "43b74ef7c5b2cc719fa8057c771db0aa7d2fac9e"
}
],
"source": "REFERENCES_TAG"
}
]
}