CVE-2025-64484 Details
Description
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 prior to 7.13.0, all deployments of OAuth2 Proxy in front of applications that normalize underscores to dashes in HTTP headers (e.g., WSGI-based frameworks such as Django, Flask, FastAPI, and PHP applications). Authenticated users can inject underscore variants of X-Forwarded-* headers that bypass the proxy’s filtering logic, potentially escalating privileges in the upstream app. OAuth2 Proxy authentication/authorization itself is not compromised. The problem has been patched with v7.13.0. By default all specified headers will now be normalized, meaning that both capitalization and the use of underscores (_) versus dashes (-) will be ignored when matching headers to be stripped. For example, both `X-Forwarded-For` and `X_Forwarded-for` will now be treated as equivalent and stripped away. For those who have a rational that requires keeping a similar looking header and not stripping it, the maintainers introduced a new configuration field for Headers managed through the AlphaConfig called `InsecureSkipHeaderNormalization`. As a workaround, ensure filtering and processing logic in upstream services don't treat underscores and hyphens in Headers the same way.
A vulnerability in OAuth2-Proxy versions prior to 7.13.0 allows authenticated users to inject underscore variants of X-Forwarded-* headers. This injection can bypass the proxy's header filtering and potentially escalate privileges in upstream applications that normalize underscores to dashes, such as those built with WSGI frameworks like Django, Flask, FastAPI, or certain PHP applications. The issue arises because the proxy does not properly handle header names with underscores, which are dropped by default in Nginx but can be exploited in Apache.
Users can update to OAuth2-Proxy version 7.13.0 or later, where this vulnerability has been patched. For those who need to maintain similar-looking headers without stripping them, a new configuration option called 'InsecureSkipHeaderNormalization' can be used.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Nov 10, 2025CISA-ADP
Assessed Nov 14, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-644 | Improper Neutralization of HTTP Headers for Scripting Syntax | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| OAuth2-Proxy | <= 7.12.0 (semver) |
CPE
Remediation
| |
| Django | All versions |
CPE
Remediation
| |
| Flask | All versions |
CPE
Remediation
| |
| FastAPI | All versions |
CPE
Remediation
| |
| PHP | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 10, 2025 | New CVE Received | [email protected] |
Volerion