Vulnerability in github.com/external-secrets/external-secrets (CVE-2026-42875)
Summary
Vulnerability in github.com/external-secrets/external-secrets (CVE-2026-42875). Risk of unauthorized operations or information disclosure. Exploitable via ConfigMap. Mitigation: upgrade to 2.4.0 or later.
Original description
The description as published by the source.
External Secrets Operator reads information from a third-party service and automatically injects the values as Kubernetes Secrets. Prior to 2.4.0, 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. This vulnerability is fixed in 2.4.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42875 has been found in github.com/external-secrets/external-secrets.
Attackers can target a specific entry point like ConfigMap over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/external-secrets/external-secrets to 2.4.0 or later.
If unsure, ask your IT team or search "github.com/external-secrets/external-secrets CVE-2026-42875" on the vendor's site.
CVE-2026-42875 (github.com/external-secrets/external-secrets) — CWE-285
Attack surface: ConfigMap / caProvider.namespace
Patched: 2.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in github.com/external-secrets/external-secrets. Attackers reach the vulnerable code path via ConfigMap.
Check the vendor advisory for the affected versions of github.com/external-secrets/external-secrets. Attack surface: ConfigMap / caProvider.namespace.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/external-secrets/external-secrets' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/external-secrets/external-secrets' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/external-secrets/external-secretsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/external-secrets/external-secrets to 2.4.0ステージング環境で 2.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com