Advisory record · GHSA-pxq7-h93f-9jrg

OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex

CVSS 8.2 HighEPSS 0.0029 · 21st percentile

Published by the GitHub Advisory Database at 15 Apr 2026, 19:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/oauth2-proxy/oauth2-proxy/v7Go>=7.5.0, <7.15.27.15.2
Identifiers
GHSA-pxq7-h93f-9jrg · BIT-oauth2-proxy-2026-41059 · CVE-2026-41059 · GO-2026-5559
Weakness (CWE)
CWE-288
Published
15 Apr 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions 7.5.0 up to but not including 7.15.2 of the Go module github.com/oauth2-proxy/oauth2-proxy/v7 are affected when skip_auth_routes or the legacy skip_auth_regex uses broadly wildcarded patterns and the protected upstream treats "#" as a fragment delimiter. An unauthenticated attacker can send a request with a number sign (or %23) in the path to match a public rule and reach a protected backend resource. Upgrade to version 7.15.2; until then, tighten skip-auth patterns to exact paths and reject requests containing "#" or "%23" at the ingress, load balancer, or WAF.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0029, the 21st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 22 Apr 2026, 00:16 UTC Confirmed by NVD
  2. 31 Oct 2026, 15:06 UTC First seen by agentprime
  3. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.