Cross-namespace secret disclosure via unchecked namespace references
Published Oct 10, 2025 · Updated Oct 14, 2025
Improper access control in External Secrets Operator 0.10.1 through 0.19.2 allows attackers to read cross-namespace Kubernetes Secrets. The BeyondTrust provider directly dereferences namespace-qualified Kubernetes Secret keys without validating the store kind or namespace boundary. Reachability requires control of a BeyondTrust provider configuration that references another namespace, and exposure is limited to Secrets readable by the controller.
Summary
What happened
Improper access control in External Secrets Operator 0.10.1 through 0.19.2 allows attackers to read cross-namespace Kubernetes Secrets. The BeyondTrust provider directly dereferences namespace-qualified Kubernetes Secret keys without validating the store kind or namespace boundary. Reachability requires control of a BeyondTrust provider configuration that references another namespace, and exposure is limited to Secrets readable by the controller.
The record
- CVE
- CVE-2025-62159
- Published
- Oct 10, 2025
- Updated
- Oct 14, 2025
- Vendor
- External Secrets
- Product
- External Secrets Operator
- Classifications
- CWE-284, T1552.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.10.1, < 0.20.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo