Aiven Operator

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:aiven:aiven_operator:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorAiven (55dae46f-23ce-5560-8065-cd68a0390f60)
ProductAiven Operator (b20870e7-6323-5ac9-9e83-dcc3c7db9666)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/aiven/aiven-operator purl2cpe 2026-06-01 10:18:08.287958
pkg:golang/github.com/aiven/aiven-operator purl2cpe 2026-06-01 10:18:08.287961

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-39961 vulnerable 2026-06-08 08:01:17.241458 Aiven Operator has cross-namespace secret exfiltration via ClickhouseUser connInfoSecretSource
MEDIUM (6.8)
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.
Published: 2026-04-09T17:14:07.330Z
Updated: 2026-04-10T14:08:22.087Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.