Cyber Resilience

CVE-2025-54576

Auth Bypass in Oauth2 Proxy Project Oauth2 Proxy ≤ 7.11.0

Public PoCAuth Bypass
Published
30 July 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.011 64th percentile
Risk Priority 69 floored blend · peak EPSS

Summary

CVE-2025-54576 is a critical-severity Authentication Bypass by Spoofing (CWE-290) vulnerability in Oauth2 Proxy Project Oauth2 Proxy. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked in the top 36% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-54576 is a high-severity authentication bypass vulnerability (CVSS 3.1 score of 9.1, CWE-290) in OAuth2-Proxy, an open-source tool that functions as a standalone reverse proxy or middleware integrated into existing reverse proxies or load balancers. It affects versions 7.10.0 and below when the skip_auth_routes configuration option is used with regex patterns. The flaw occurs because skip_auth_routes matching is performed against the full request URI, including query parameters, allowing attackers to craft malicious URLs that satisfy the regex patterns and bypass authentication checks for protected resources. Deployments with wildcard or broad matching patterns in skip_auth_routes are particularly at risk.

Any network-accessible attacker (AV:N/AC:L/PR:N) can exploit this vulnerability without user interaction or privileges by sending crafted requests with query parameters that trigger a regex match on skip_auth_routes. Successful exploitation grants unauthorized access to protected resources, potentially leading to high confidentiality and integrity impacts (C:H/I:H) such as data exposure or modification, depending on the backend services.

The vulnerability is fixed in OAuth2-Proxy version 7.11.0. Mitigation guidance from the GitHub security advisory (GHSA-7rh7-c77v-6434) and release notes includes auditing all skip_auth_routes configurations for overly permissive patterns, replacing wildcards with exact path matches where possible, anchoring regex patterns with ^ and $, or implementing custom validation that strips query parameters before matching. Relevant code changes and commit details are available in the project's GitHub repository.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

OAuth2-Proxy is an open-source tool that can act as either a standalone reverse proxy or a middleware component integrated into existing reverse proxy or load balancer setups. In versions 7.10.0 and below, oauth2-proxy deployments are vulnerable when using the skip_auth_routes…

more

configuration option with regex patterns. Attackers can bypass authentication by crafting URLs with query parameters that satisfy configured regex patterns, allowing unauthorized access to protected resources. The issue stems from skip_auth_routes matching against the full request URI. Deployments using skip_auth_routes with regex patterns containing wildcards or broad matching patterns are most at risk. This issue is fixed in version 7.11.0. Workarounds include: auditing all skip_auth_routes configurations for overly permissive patterns, replacing wildcard patterns with exact path matches where possible, ensuring regex patterns are properly anchored (starting with ^ and ending with $), or implementing custom validation that strips query parameters before regex matching.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
T1557.001 Name Resolution Poisoning and SMB Relay Credential Access
By responding to LLMNR/NBT-NS/mDNS network traffic, adversaries may spoof an authoritative source for name resolution to force communication with an adversary controlled system.
T1036 Masquerading Stealth
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
T1036.001 Invalid Code Signature Stealth
Adversaries may attempt to mimic features of valid code signatures to increase the chance of deceiving a user, analyst, or tool.
T1134 Access Token Manipulation Stealth
Adversaries may modify access tokens to operate under a different user or system security context to perform actions and bypass access controls.
T1134.001 Token Impersonation/Theft Stealth
Adversaries may duplicate then impersonate another user's existing token to escalate privileges and bypass access controls.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34457Same product: Oauth2 Proxy Project Oauth2 Proxy
CVE-2026-40575Same product: Oauth2 Proxy Project Oauth2 Proxy
CVE-2026-34454Same product: Oauth2 Proxy Project Oauth2 Proxy
CVE-2026-41059Same product: Oauth2 Proxy Project Oauth2 Proxy
CVE-2026-40574Same product: Oauth2 Proxy Project Oauth2 Proxy
CVE-2025-36119Shared CWE-290
CVE-2024-8901Shared CWE-290
CVE-2026-33433Shared CWE-290
CVE-2023-44117Shared CWE-290
CVE-2025-0440Shared CWE-290

Affected Assets

oauth2 proxy project
oauth2 proxy
≤ 7.11.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.4.3
  • V10.4.16
  • V10.5.1
  • V11.4.3

Mitigating Controls (NIST 800-53 r5) AI

Proper unique identification and authentication of users directly stops spoofing-based bypass of authentication.

Device identification and authentication before connection prevents spoofing of devices to bypass auth.

Authentication of non-organizational users blocks external spoofing attempts against the scheme.

Authenticator management ensures credentials cannot be easily spoofed or reused to bypass authentication.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-04 full match
prevents

Protecting, conveying, and verifying identity assertions specifically prevents the spoofing that enables authentication bypass.

PR.AA-03 mostly match
prevents

Requiring authentication of users/services/hardware directly counters spoofing-based bypass when strong methods are used.

PR.AA-02 partial match
prevents

Proofing and binding identities reduces spoofing opportunities during enrollment but does not address runtime authentication implementation flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Secure authentication control directly mitigates authentication bypass by spoofing.

degrades

Authentication information management directly addresses credential handling that prevents spoofing.

finds

Security testing can detect spoofing vulnerabilities but does not prevent them by itself.

prevents

Access control policy reduces spoofing opportunities but does not prescribe authentication mechanisms.

prevents

Identity management supports unique identities but does not guarantee resistance to spoofing.

prevents

Access rights assignment limits exposure but does not enforce authentication strength.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-290
RHEL 7 (1 rule)
  • V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-290
RHEL 8 (1 rule)
  • V-230492 RHEL 8 must not have the rsh-server package installed. prevents CWE-290

References