Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2026-34454

3.5 · LOW
Published Apr 14, 2026 oauth2_proxy_project CWE-384

Overview

CVE-2026-34454 is a low-severity vulnerability affecting oauth2_proxy_project oauth2_proxy. It was published on April 14, 2026 and has a CVSS 3.1 base score of 3.5 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.5, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical Description

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

Remediation

Check the references section for vendor advisories and patches from oauth2_proxy_project. Update oauth2_proxy to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
oauth2_proxy_project oauth2_proxy >= 7.11.0, < 7.15.2 Affected

Frequently Asked Questions

What is CVE-2026-34454?

CVE-2026-34454 is a low-severity vulnerability affecting oauth2_proxy_project oauth2_proxy. It was published on April 14, 2026 and has a CVSS 3.1 base score of 3.5 (LOW).

How severe is CVE-2026-34454?

This vulnerability has a CVSS 3.1 base score of 3.5, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-34454?

Check the references section for vendor advisories and patches from oauth2_proxy_project. Update oauth2_proxy to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-34454?

CyberStrike's AI-powered security agents can automatically detect CVE-2026-34454 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.