CVE-2026-39961 json
Aiven Operator has cross-namespace secret exfiltration via ClickhouseUser connInfoSecretSource
published 7mo ago modified 14d ago also GHSA-99j8-wv67-4c72 , GO-2026-5283 , EUVD-2026-20965
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/aiven/aiven-operator 0.37.0
- aiven aiven_operator 0.37.0
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2026-39961 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N |
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/aiven/aiven-operator | >=0.31.0, <0.37.0 |
0.37.0 |
Affected products
- aiven aiven-operator
Classification
References
-
github.com
/aiven/aiven-operator/commit/032c9ba63257fdd2fddfb7f73f71830e371ff182
web, patch
-
github.com
/aiven/aiven-operator/security/advisories/GHSA-99j8-wv67-4c72
web, vendor-advisory, advisory
-
github.com
/aiven/aiven-operator/releases/tag/v0.37.0
web, product, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-39961
advisory
-
github.com
/aiven/aiven-operator
package
Sources
- CVE List CVE-2026-39961
- GitHub Advisory GHSA-99j8-wv67-4c72
- NVD CVE-2026-39961
- OSV GO-2026-5283
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.