GHSA-pxq7-h93f-9jrg
HIGHGHSA-pxq7-h93f-9jrg is a high-severity (CVSS 8.2) CWE-288 vulnerability in github.com/oauth2-proxy/oauth2-proxy/v7. O3 Security confirms whether GHSA-pxq7-h93f-9jrg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-pxq7-h93f-9jrg.
Real-World Exposure
github.com/oauth2-proxy/oauth2-proxy/v7Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A configuration-dependent authentication bypass exists in OAuth2 Proxy.
Deployments are affected when all of the following are true:
- Use of
skip_auth_routesor the legacyskip_auth_regex* Use of patterns that can be widened by attacker-controlled suffixes, such as^/foo/.*/bar$causing potential exposure of/foo/secret* Protected upstream applications that interpret#as a fragment delimiter or otherwise route the request to the protected base path
In deployments that rely on these settings, an unauthenticated attacker can send a crafted request containing a number sign in the path, including the browser-safe encoded form %23, so that OAuth2 Proxy matches a public allowlist rule while the backend serves a protected resource.
Deployments that do not use these skip-auth options, or that only allow exact public paths with tightly scoped method and path rules, ARE NOT affected.
Patches
A fix has been implemented to normalize request paths more conservatively before skip-auth matching so fragment content does not influence allowlist decisions.
Released as part of v7.15.2
Workarounds
Users who cannot upgrade immediately can reduce exposure by tightening or removing skip_auth_routes and skip_auth_regex rules, especially patterns that use broad wildcards across path segments.
Recommended mitigations:
- Replace broad rules with exact, anchored public paths and explicit HTTP methods
- Reject requests whose path contains
%23or#at the ingress, load balancer, or WAF level - Avoid placing sensitive application paths behind broad
skip_auth_routesrules
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/oauth2-proxy/oauth2-proxy/v7 | ≥ 7.5.0&&< 7.15.2 | 7.15.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/oauth2-proxy/oauth2-proxy/v7. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/oauth2-proxy/oauth2-proxy/v7 to 7.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pxq7-h93f-9jrg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pxq7-h93f-9jrg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-pxq7-h93f-9jrg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pxq7-h93f-9jrg in your dependencies?
O3 detects GHSA-pxq7-h93f-9jrg across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.