Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/aiven/aiven-operator

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.8GoPublished

    Aiven Operator has cross-namespace secret exfiltration via ClickhouseUser connInfoSecretSource

    CVE-2026-39961 · GHSA-99j8-wv67-4c72

    Affected
    • Go github.com/aiven/aiven-operator >= 0.31.0, < 0.37.0
    Fixed in
    0.37.0· Vendor fix available
    Issue
    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

    Recommended action: Upgrade to 0.37.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →