CVE-2026-34454: Github.com/oauth2 proxy/oauth2 proxy/v7 OAuth2 Proxy's Session Cookies Are Vulnerability
LOWCVE-2026-34454 is a LOW (CVSS 3.5) oauth2 proxy's session cookies are vulnerability (CWE-613: Insufficient Session Expiration) affecting Github.com/oauth2 proxy/oauth2 proxy/v7 libraries in the Go ecosystem. The issue involves oauth2 proxy's session cookies are not cleared when rendering sign-in page. Remediation is available by upgrading affected packages to version 7.15.2.
CVE-2026-34454 at a Glance
Security Impact
CVSS: 3.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).
How to Fix CVE-2026-34454
To remediate this vulnerability, upgrade all affected Github.com/oauth2 proxy/oauth2 proxy/v7 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/oauth2-proxy/oauth2-proxy/v7 to 7.15.2Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/oauth2-proxy/oauth2-proxy/v7How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-34454, inspect your project dependencies for Github.com/oauth2 proxy/oauth2 proxy/v7:
inspect dependencies for github.com/oauth2-proxy/oauth2-proxy/v7Analyze the terminal output to locate any version of Github.com/oauth2 proxy/oauth2 proxy/v7 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.15.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-613: Insufficient Session Expiration, where according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". In Github.com/oauth2 proxy/oauth2 proxy/v7, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-34454 Affected Github.com/oauth2 proxy/oauth2 proxy/v7 Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/oauth2-proxy/oauth2-proxy/v7
|
Go |
≥ 7.11.0
< 7.15.2
|
7.15.2
|
References
Frequently Asked Questions
What is CVE-2026-34454?
Which Github.com/oauth2 proxy/oauth2 proxy/v7 versions are affected?
What version fixes CVE-2026-34454?
Is github.com/oauth2-proxy/oauth2-proxy/v7 affected?
What is the CVSS score of CVE-2026-34454?
What CWE is associated with CVE-2026-34454?
How can I check Go dependencies for CVE-2026-34454?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-f24x-5g9q-753f",
"modified" : "2026-04-15T21:06:34Z",
"published" : "2026-04-14T22:31:03Z",
"aliases" : [ "CVE-2026-34454" ],
"summary" : "OAuth2 Proxy's session cookies are not cleared when rendering sign-in page",
"details" : "### Impact\nA regression introduced in [v7.11.0](https://github.com/oauth2-proxy/oauth2-proxy/pull/2605) is preventing OAuth2 Proxy from clearing the session cookie when rendering the sign-in page.\n\nThis only impacts deployments that rely on the sign-in page as part of their logout flow. In those setups, a user may be shown the sign-in page while the existing session cookie remains valid, so the browser session is not actually logged out. On shared workstations be it browsers or devices, a subsequent user could continue to use the previous user's authenticated session.\n\nDeployments that use a dedicated logout/sign-out endpoint to terminate sessions are not affected.\n\n### Patches\nThis issue is fixed in v7.15.2.\n\n### Workarounds\nDo not rely on the sign-in page to clear an existing session. Instead:\n\n- Use the dedicated logout/sign-out endpoint of OAuth2 Proxy\n- Ensure your application logout flow explicitly clears the OAuth2 Proxy session cookie before redirecting users to the sign-in page\n- If needed, clear the session cookie at the reverse proxy or application layer as a temporary mitigation",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/oauth2-proxy/oauth2-proxy/v7"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "7.11.0"
}, {
"fixed" : "7.15.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-f24x-5g9q-753f"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34454"
}, {
"type" : "WEB",
"url" : "https://github.com/oauth2-proxy/oauth2-proxy/pull/2605"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/oauth2-proxy/oauth2-proxy"
}, {
"type" : "WEB",
"url" : "https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.15.2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-384", "CWE-613" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-14T22:31:03Z",
"nvd_published_at" : "2026-04-14T23:16:28Z"
}
}