CVE-2025-64484: OAuth2-Proxy is vulnerable to header smuggling via underscore leading to potential privilege escalation

CVE-2025-64484 · Severity: low · CVSS 3.1 · Published 2025-11-17

OAuth2-Proxy is vulnerable to header smuggling via underscore leading to potential privilege escalation in github.com/oauth2-proxy/oauth2-proxy

Technologies: github.com/oauth2-proxy/oauth2-proxy (Go), github.com/oauth2-proxy/oauth2-proxy/v7 (Go). Vendors: Go.

Quick answers

Is CVE-2025-64484 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-64484 being exploited in the wild.
How severe is CVE-2025-64484?
Low severity, with a CVSS score of 3.1, published 17 November 2025.
Which products and versions are affected?
github.com/oauth2-proxy/oauth2-proxy (Go) SEMVER:introduced=0; github.com/oauth2-proxy/oauth2-proxy/v7 (Go) SEMVER:introduced=0,fixed=7.13.0.
Is there a fix for CVE-2025-64484?
Yes. github.com/oauth2-proxy/oauth2-proxy/v7 (Go): upgrade to 7.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-64484?
Check whether you run github.com/oauth2-proxy/oauth2-proxy (Go) or github.com/oauth2-proxy/oauth2-proxy/v7 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/oauth2-proxy/oauth2-proxy/v7 (Go): upgrade to 7.13.0 or later
    go get github.com/oauth2-proxy/oauth2-proxy/v7@v7.13.0

Affected products

  • github.com/oauth2-proxy/oauth2-proxy (Go) SEMVER:introduced=0
  • github.com/oauth2-proxy/oauth2-proxy/v7 (Go) SEMVER:introduced=0,fixed=7.13.0

Identifiers

  • CVE-2025-64484
  • GHSA-vjrc-mh2v-45x6
  • GO-2025-4113

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.