CVE-2026-34454 | oauth2-proxy OAuth2 Proxy up to 7.15.1 Logout/Sign-out session expiration (GHSA-f24x-5g9q-753f)

VDB-357656 · CVE-2026-34454 · GHSA-F24X-5G9Q-753F OAUTH2-PROXY OAUTH2 PROXY UP TO 7.15.1 LOGOUT/SIGN-OUT SESSION EXPIRATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.3 $0-$5k 2.04+ Summaryinfo A vulnerability described as critical has been identified in oauth2-proxy OAuth2 Proxy up to 7.15.1. This affects an unknown part of the component Logout/Sign-out. Such manipulation leads to session expiration. This vulnerability is documented as CVE-2026-34454. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is recommended. Detailsinfo A vulnerability was found in oauth2-proxy OAuth2 Proxy up to 7.15.1 and classified as critical. Affected by this issue is an unknown code block of the component Logout/Sign-out. The manipulation with an unknown input leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality, integrity, and availability. CVE summarizes: 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 The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-34454 since 03/27/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. Upgrading to version 7.15.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Productinfo Type Firewall Software Vendor oauth2-proxy Name OAuth2 Proxy Version 7.15.0 7.15.1 CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.4 VulDB Meta Temp Score: 5.3 VulDB Base Score: 7.3 VulDB Temp Score: 7.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 3.5 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Session expiration CWE: CWE-613 CAPEC: 🔒 ATT&CK: 🔒 Physical: Yes Local: Partially Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: OAuth2 Proxy 7.15.2 Timelineinfo 03/27/2026 CVE reserved 04/15/2026 +18 days Advisory disclosed 04/15/2026 +0 days VulDB entry created 04/15/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-f24x-5g9q-753f Status: Confirmed CVE: CVE-2026-34454 (🔒) GCVE (CVE): GCVE-0-2026-34454 GCVE (VulDB): GCVE-100-357656 Entryinfo Created: 04/15/2026 07:19 Changes: 04/15/2026 07:19 (66) Complete: 🔍 Cache ID: 99:748:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸