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.
Original description
The description as published by the source.
OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. A regression introduced in 7.11.0 prevents OAuth2 Proxy from clearing the session cookie when rendering the sign-in page. In deployments that rely on the sign-in page as part of their logout flow, a user may be shown the sign-in page while the existing session cookie remains valid, meaning the browser session is not actually logged out. On shared workstations or devices, a subsequent user could continue to use the previous user's authenticated session. Deployments that use a dedicated logout/sign-out endpoint to terminate sessions are not affected. This issue is fixed in 7.15.2
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-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.
A vulnerability (CWE-384) exists in oauth2-proxy.
Check the vendor advisory for the affected versions of oauth2-proxy.
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.
Update to 7.15.2.
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 'oauth2-proxy' . 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 'oauth2-proxy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
oauth2-proxyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade oauth2-proxy to 7.15.2ステージング環境で 7.15.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- patch github.com
- web github.com