CVE-2026-39961: Aiven Operator has cross-namespace secret exfiltration via ClickhouseUser connInfoSecretSource

Published Apr 9, 2026
·
Updated

Impact 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.

Patches

This vulnerability is resolved in version 0.37.0. We recommend all users update as soon as possible.

Credits

Credits to Andrés Cruciani for finding and reporting the bug through our bug bounty program

Other sources

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.

NVD

Affected Software

2 affected componentsFixes available
go/github.com/aiven/aiven-operator>=0.31.0<0.37.0
0.37.0
aiven Aiven Operator>=0.31.0<0.37.0

Event History

Apr 9, 2026
CVE Published
via MITRE·05:14 PM
Data Sourced
via MITRE·05:14 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
RemedyAffected Software
Apr 10, 2026
Advisory Published
via GitHub·05:22 PM
Data Sourced
via GitHub·05:22 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-39961?

CVE-2026-39961 has been classified with a high severity due to the potential for unauthorized secret exfiltration from multiple namespaces.

2

How do I fix CVE-2026-39961?

To fix CVE-2026-39961, upgrade the Aiven Operator to version 0.37.0 or later.

3

Who is affected by CVE-2026-39961?

Developers with create permission on ClickhouseUser CRDs in their namespace are affected by CVE-2026-39961.

4

What types of sensitive information can be exfiltrated through CVE-2026-39961?

CVE-2026-39961 allows exfiltration of sensitive information such as production database credentials, API keys, and service tokens.

5

When was CVE-2026-39961 disclosed?

CVE-2026-39961 was disclosed as part of the security advisories related to the Aiven Operator's vulnerabilities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203