How severe is GHSA-wv26-88m5-6h59?

No CVSS score has been assigned to GHSA-wv26-88m5-6h59 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wv26-88m5-6h59?

GHSA-wv26-88m5-6h59 affects the following packages: github.com/external-secrets/external-secrets (Go). Ecosystems affected: Go.

How do I fix GHSA-wv26-88m5-6h59?

Update github.com/external-secrets/external-secrets to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wv26-88m5-6h59 is resolved across your whole dependency graph.

How do I detect GHSA-wv26-88m5-6h59 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/external-secrets/external-secrets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wv26-88m5-6h59 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-wv26-88m5-6h59?

O3 pinpoints whether GHSA-wv26-88m5-6h59 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wv26-88m5-6h59 actively exploited in the wild?

No public exploit code has been indexed for GHSA-wv26-88m5-6h59 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-wv26-88m5-6h59 published, and has it been updated?

GHSA-wv26-88m5-6h59 was published on May 5, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-wv26-88m5-6h59

GHSA-wv26-88m5-6h59 is a security vulnerability in github.com/external-secrets/external-secrets. O3 Security confirms whether GHSA-wv26-88m5-6h59 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

External Secrets Operator has Namespace Isolation Bypass in CAProvider ConfigMap Resolution for SecretStore

Also known asCVE-2026-42875GO-2026-5723

Published

May 5, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐹github.com/external-secrets/external-secrets

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/external-secrets/external-secrets`	all versions	2.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/external-secrets/external-secrets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/external-secrets/external-secrets to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wv26-88m5-6h59 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wv26-88m5-6h59 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wv26-88m5-6h59. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 mak

O3 Security · Impact-Aware SCA

Is GHSA-wv26-88m5-6h59 in your dependencies?

O3 detects GHSA-wv26-88m5-6h59 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works