CVE-2026-49332

HIGHPre-NVD 8.58.5—
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-28. a secondary CVSS source baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in openshift/oauth-proxy. The proxy sets authenticated identity headers using only dash-variant keys (X-Forwarded-User) but does not strip underscore-variant keys (X_Forwarded_User) from incoming requests. WSGI and PHP frameworks normalize both variants to the same variable, allowing an authenticated low-privilege user to smuggle a forged identity that may override the legitimate authenticated identity in the upstream application.

CVSS v3
8.5
EG Score
8.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

July 28, 2026

Last Modified

August 20, 2026

Advisory Details (2)

Auto-updated Jul 28, 2026
Patch available. Sources: redhat.
redhat

2483253 – (CVE-2026-49332) CVE-2026-49332 openshift/oauth-proxy: openshift/oauth-proxy: underscore header smuggling enables identity impersonation on WSGI/PHP upstreams

https://bugzilla.redhat.com/show_bug.cgi?id=2483253
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-49332

Vendor Advisories for CVE-2026-49332(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-oauth-proxy:17864774362026-08-20redhat
redhatopenshift4/ose-oauth-proxy:17864587042026-08-20redhat
redhatopenshift4/ose-oauth-proxy-rhel9:17855217282026-08-12redhat
redhatopenshift4/ose-oauth-proxy-rhel9:17855440392026-08-12redhat
redhatopenshift4/ose-oauth-proxy-rhel9:17855297352026-08-12redhat
redhatopenshift4/ose-oauth-proxy:17855498182026-08-12redhat
redhatopenshift4/ose-oauth-proxy-rhel9:17858513592026-08-11redhat
redhatopenshift4/ose-oauth-proxy-rhel9:17858337422026-08-11redhat
redhatopenshift4/ose-oauth-proxy-rhel9:17858853512026-08-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 65× in last 7d / 161× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-08-21 04:24 UTCEG score recompute
  2. 2026-08-21 04:24 UTCVendor advisory
  3. 2026-08-21 04:24 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 17:35 UTCEG score recompute
  6. 2026-08-20 17:35 UTCVendor advisory
  7. 2026-08-20 17:35 UTCGHSA enrichment
  8. 2026-08-20 16:46 UTCEG score recompute
  9. 2026-08-20 16:46 UTCVendor advisory
  10. 2026-08-20 16:46 UTCGHSA enrichment
  11. 2026-08-20 14:25 UTCEG score recompute
  12. 2026-08-20 14:25 UTCVendor advisory
  13. 2026-08-20 14:25 UTCGHSA enrichment
  14. 2026-08-20 13:57 UTCEG score recompute
  15. 2026-08-20 13:57 UTCVendor advisory
  16. 2026-08-20 13:57 UTCGHSA enrichment
  17. 2026-08-20 06:36 UTCVendor advisory
  18. 2026-08-20 06:36 UTCGHSA enrichment
  19. 2026-08-19 19:47 UTCEG score recompute
  20. 2026-08-19 19:47 UTCVendor advisory
  21. 2026-08-19 19:47 UTCGHSA enrichment
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-19 07:20 UTCEG score recompute
  24. 2026-08-19 07:20 UTCVendor advisory
  25. 2026-08-19 07:20 UTCGHSA enrichment
Show 75 more
  1. 2026-08-19 06:52 UTCVendor advisory
  2. 2026-08-19 06:52 UTCGHSA enrichment
  3. 2026-08-19 05:29 UTCVendor advisory
  4. 2026-08-19 05:29 UTCGHSA enrichment
  5. 2026-08-18 18:40 UTCEG score recompute
  6. 2026-08-18 18:40 UTCVendor advisory
  7. 2026-08-18 18:40 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 06:02 UTCVendor advisory
  10. 2026-08-18 06:02 UTCGHSA enrichment
  11. 2026-08-18 05:31 UTCEG score recompute
  12. 2026-08-18 05:31 UTCVendor advisory
  13. 2026-08-18 05:31 UTCGHSA enrichment
  14. 2026-08-17 19:57 UTCEG score recompute
  15. 2026-08-17 19:57 UTCVendor advisory
  16. 2026-08-17 19:57 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 08:08 UTCVendor advisory
  19. 2026-08-17 08:08 UTCGHSA enrichment
  20. 2026-08-16 21:20 UTCEG score recompute
  21. 2026-08-16 21:20 UTCVendor advisory
  22. 2026-08-16 21:20 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 10:31 UTCEG score recompute
  25. 2026-08-16 10:31 UTCVendor advisory
  26. 2026-08-16 10:31 UTCGHSA enrichment
  27. 2026-08-16 09:41 UTCEG score recompute
  28. 2026-08-16 09:41 UTCVendor advisory
  29. 2026-08-16 09:41 UTCGHSA enrichment
  30. 2026-08-16 02:14 UTCEPSS rescore
  31. 2026-08-16 01:03 UTCVendor advisory
  32. 2026-08-16 01:03 UTCGHSA enrichment
  33. 2026-08-15 14:14 UTCVendor advisory
  34. 2026-08-15 14:14 UTCGHSA enrichment
  35. 2026-08-15 03:25 UTCEG score recompute
  36. 2026-08-15 03:25 UTCVendor advisory
  37. 2026-08-15 03:25 UTCGHSA enrichment
  38. 2026-08-15 01:30 UTCEPSS rescore
  39. 2026-08-14 16:36 UTCVendor advisory
  40. 2026-08-14 16:36 UTCGHSA enrichment
  41. 2026-08-14 05:48 UTCEG score recompute
  42. 2026-08-14 05:48 UTCVendor advisory
  43. 2026-08-14 05:48 UTCGHSA enrichment
  44. 2026-08-13 22:00 UTCEPSS rescore
  45. 2026-08-13 18:59 UTCVendor advisory
  46. 2026-08-13 18:59 UTCGHSA enrichment
  47. 2026-08-13 08:11 UTCVendor advisory
  48. 2026-08-13 08:10 UTCGHSA enrichment
  49. 2026-08-12 21:22 UTCEG score recompute
  50. 2026-08-12 21:22 UTCVendor advisory
  51. 2026-08-12 21:22 UTCGHSA enrichment
  52. 2026-08-12 21:09 UTCEG score recompute
  53. 2026-08-12 21:09 UTCVendor advisory
  54. 2026-08-12 21:09 UTCGHSA enrichment
  55. 2026-08-12 16:36 UTCEG score recompute
  56. 2026-08-12 16:36 UTCVendor advisory
  57. 2026-08-12 16:36 UTCGHSA enrichment
  58. 2026-08-12 15:37 UTCEG score recompute
  59. 2026-08-12 15:37 UTCVendor advisory
  60. 2026-08-12 15:37 UTCGHSA enrichment
  61. 2026-08-12 13:51 UTCEPSS rescore
  62. 2026-08-12 08:20 UTCVendor advisory
  63. 2026-08-12 08:20 UTCGHSA enrichment
  64. 2026-08-12 08:01 UTCVendor advisory
  65. 2026-08-12 08:00 UTCGHSA enrichment
  66. 2026-08-11 21:11 UTCEG score recompute
  67. 2026-08-11 21:11 UTCVendor advisory
  68. 2026-08-11 21:11 UTCGHSA enrichment
  69. 2026-08-11 10:23 UTCEG score recompute
  70. 2026-08-11 10:23 UTCGHSA enrichment
  71. 2026-08-11 10:02 UTCEG score recompute
  72. 2026-08-11 10:02 UTCGHSA enrichment
  73. 2026-08-11 09:24 UTCEG score recompute
  74. 2026-08-11 09:24 UTCGHSA enrichment
  75. 2026-08-11 09:14 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49332?
CVE-2026-49332 is a high vulnerability published on July 28, 2026. A flaw was found in openshift/oauth-proxy. The proxy sets authenticated identity headers using only dash-variant keys (X-Forwarded-User) but does not strip underscore-variant keys (XForwardedUser) from incoming requests. WSGI and PHP frameworks normalize both variants to the same variable, allowing…
When was CVE-2026-49332 disclosed?
CVE-2026-49332 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49332 actively exploited?
CVE-2026-49332 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.2% of all scored CVEs.
What is the CVSS score of CVE-2026-49332?
CVE-2026-49332 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-49332?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49332, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49332

Explore →

Is Your Infrastructure Affected by CVE-2026-49332?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs