Quick answers
- Is CVE-2026-42875 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42875 being exploited in the wild.
- How severe is CVE-2026-42875?
- Medium severity, with a CVSS score of 4, published 11 May 2026.
- Which products and versions are affected?
- External Secrets Operator < 2.4.0; github.com/external-secrets/external-secrets (Go) < 2.4.0, SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.4.0.
- Is there a fix for CVE-2026-42875?
- Yes. github.com/external-secrets/external-secrets (Go): upgrade to 2.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42875 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-42875?
- Check whether you run External Secrets Operator or github.com/external-secrets/external-secrets (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/external-secrets/external-secrets (Go): upgrade to 2.4.0 or later
go get github.com/external-secrets/external-secrets@v2.4.0
Technical details
A namespace isolation bypass exists in External Secrets Operator when using CAProvider with type ConfigMap. Namespaced SecretStore resources could resolve CA material from a different namespace if the caProvider.namespace field was explicitly set, bypassing the intended security boundary enforced by the shared runtime CA resolver. An attacker with low privileges can exploit this to infer the existence of ConfigMaps or keys in other namespaces or force a SecretStore to consume unauthorized CA material. The vulnerability is patched in version 2.4.0.
Affected products
- external-secrets external-secrets < 2.4.0
Identifiers
- CVE-2026-42875
- GHSA-wv26-88m5-6h59
- GO-2026-5723
Timeline
- 2026-04-24: disclosed: Vulnerability reported by moolen
- 2026-05-05: advisory: GitHub Advisory published
- 2026-05-11: other: NVD publication date