← Back
CVE-2026-34454
low
CVSS 3.5
Vulnerability in oauth2-proxy (CVE-2026-34454)
Summary
vulnerability in oauth2-proxy (CVE-2026-34454). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `7.15.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-34454** has been found in oauth2-proxy.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: upgrade oauth2-proxy to **7.15.2** or later.
If unsure, ask your IT team or search "oauth2-proxy CVE-2026-34454" on the vendor's site.
CVE-2026-34454 (oauth2-proxy) — CWE-384 / CVSS v3 3.5
Attack vector: physical / unauthenticated / no user interaction
Patched: `7.15.2` — 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.
❓ What is the problem
**A vulnerability** (CWE-384) exists in oauth2-proxy.
📍 Affected scope
oauth2-proxy — .
🔥 Severity
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.15.2**.
🛡️ 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 'oauth2-proxy' .` 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 'oauth2-proxy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `oauth2-proxy` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade oauth2-proxy to 7.15.2ステージング環境で 7.15.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
oauth2-proxy
[{"type":"SEMVER","events":[{"introduced":"7.11.0"},{"fixed":"7.15.2"}]}]
Go
github.com/oauth2-proxy/oauth2-proxy/v7
[{"type":"SEMVER","events":[{"introduced":"7.11.0"},{"fixed":"7.15.2"}]}]
Go
github.com/oauth2-proxy/oauth2-proxy
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
References
- advisory https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-f24x-5g9q-753f
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-34454
- package https://github.com/oauth2-proxy/oauth2-proxy
- patch https://github.com/oauth2-proxy/oauth2-proxy/pull/2605
- web https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.15.2