CVE-2026-42875: External Secrets Operator has Namespace Isolation Bypass in CAProvider ConfigMap Resolution for SecretStore
Impact Namespaced SecretStore resources that used CAProvider with type ConfigMap could resolve CA material from another namespace when caProvider.namespace was set. This bypassed the namespace boundary enforced for SecretStore-backed references in providers that rely on the shared runtime CA resolver. The accessible data is used as CA validation material, hence it is not directly exposed.
Published May 5, 2026 · Updated May 13, 2026
Affected packages
github.com/external-secrets/external-secrets
- Ecosystem
- Go
- Affected
- < 2.4.0
- Fixed in
- 2.4.0
- Check
go list -m github.com/external-secrets/external-secrets
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Namespaced SecretStore resources that used CAProvider with type ConfigMap could resolve CA material from another namespace when caProvider.namespace was set. This bypassed the namespace boundary enforced for SecretStore-backed references in providers that rely on the shared runtime CA resolver.
The accessible data is used as CA validation material, hence it is not directly exposed.
Impact:
- Direct data exfiltration risk: low
- Existence disclosure: an attacker can infer whether a target ConfigMap/key exists in another namespace.
- Trust-boundary violation: a tenant can make its SecretStore consume CA material owned by another namespace.
Credited to moolen.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-26287
External Secrets Operator: label enforcement bypass in webhook generator enables secret exfiltration
high7.1Oct 6, 2026CVE-2026-34984
External Secrets Operator has DNS-based secret exfiltration via getHostByName in External Secrets v2 template engine
high6.5No fixApr 13, 2026CVE-2026-22822
External Secrets Operator insecurely retrieves secrets through the getSecretKey templating function
critical9.3Jan 20, 2026CVE-2025-55196
External Secrets Operator's Missing Namespace Restriction Allows Unauthorized Secret Access
high7.1Aug 13, 2025CVE-2024-45041
External Secrets Operator vulnerable to privilege escalation
high8.3Sep 9, 2024
