Advisory

GHSA-f24x-5g9q-753f

Also known as: BIT-oauth2-proxy-2026-34454, CVE-2026-34454, GO-2026-5341

Summary

OAuth2 Proxy's session cookies are not cleared when rendering sign-in page

Details

Impact
A regression introduced in v7.11.0 is preventing OAuth2 Proxy from clearing the session cookie when rendering the sign-in page.

This 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.

Deployments that use a dedicated logout/sign-out endpoint to terminate sessions are not affected.

Patches
This issue is fixed in v7.15.2.

Workarounds
Do not rely on the sign-in page to clear an existing session. Instead:

  • Use the dedicated logout/sign-out endpoint of OAuth2 Proxy
  • Ensure your application logout flow explicitly clears the OAuth2 Proxy session cookie before redirecting users to the sign-in page
  • If needed, clear the session cookie at the reverse proxy or application layer as a temporary mitigation

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-04-14 22:31 UTC
Modified
2026-06-25 19:56 UTC

Affected packages and fixes

github.com/oauth2-proxy/oauth2-proxy/v7

Go · All systems

Affected

  • introduced 7.11.0, fixed 7.15.2 (semver)

Fixed versions

7.15.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences