← Back
CVE-2026-34984
Information Disclosure in github.com/external-secrets/external-secrets (CVE-2026-34984)
Summary
vulnerability in github.com/external-secrets/external-secrets (CVE-2026-34984). Confidential information can be exposed externally. Exploitable via ``env``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-34984** has been found in github.com/external-secrets/external-secrets.
Attackers can target a specific entry point like ``env`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/external-secrets/external-secrets CVE-2026-34984" on the vendor's site.
CVE-2026-34984 (github.com/external-secrets/external-secrets) — CWE-200 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `env` / `expandenv` / `getHostByName`
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.
❓ What is the problem
**information disclosure** (CWE-200) exists in github.com/external-secrets/external-secrets. Attackers reach the vulnerable code path via ``env`` without authentication.
📍 Affected scope
github.com/external-secrets/external-secrets — . Attack surface: `env` / `expandenv` / `getHostByName`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/external-secrets/external-secrets
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"last_affected":"2.2.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-34984
- package https://github.com/external-secrets/external-secrets
- web https://github.com/external-secrets/external-secrets/security/advisories/GHSA-r2pg-r6h7-crf3
- web https://github.com/external-secrets/external-secrets/commit/6800989bdc12782ca2605d3b8bf7f2876a16551a
- web https://github.com/external-secrets/external-secrets/releases/tag/v2.3.0