github.com/external-secrets/external-secrets
Affected
- introduced
0.15.0, fixed0.19.2(semver)
Fixed versions
0.19.2
Fix
- Fixed version
0.19.2go get github.com/external-secrets/[email protected]
Advisory
Also known as: CVE-2025-55196, GO-2025-3885
External Secrets Operator's Missing Namespace Restriction Allows Unauthorized Secret Access
Summary
A vulnerability was discovered in the External Secrets Operator where the List() calls for Kubernetes Secret and SecretStore resources performed by the PushSecret controller did not apply a namespace selector.
This flaw allowed an attacker to use label selectors to list and read secrets/secret-stores across the cluster, bypassing intended namespace restrictions.
---
Impact
An attacker with the ability to create or update PushSecret resources and control SecretStore configurations could exploit this vulnerability to exfiltrate sensitive data from arbitrary namespaces.
This could lead to full disclosure of Kubernetes secrets, including credentials, tokens, and other sensitive information stored in the cluster.
---
Exploitability
To exploit this vulnerability, an attacker must:
PushSecret resources.SecretStore resources.With these conditions met, the attacker could leverage label selectors to list secrets from any namespace and retrieve their contents.
---
Affected Versions
---
Fix
The vulnerability was addressed in v0.19.2 by adding namespace restrictions to the List() calls for both PushSecret and SecretStore controllers.
This ensures that only secrets in the intended namespace are accessible.
Relevant fixes:
List() calls List() calls ---
Mitigation
If upgrading to v0.19.2 or later is not immediately possible, the following mitigations are recommended:
PushSecret and SecretStore resources. PushSecret and SecretStore resources to ensure they are controlled by trusted parties. ---
Credit
This vulnerability was reported by @gracedo and @moolen
High Basis: The source's own band: HIGH
0.15.0, fixed 0.19.2 (semver)0.19.2
0.19.2go get github.com/external-secrets/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0