Impacts OpenShift oauth-proxy, widely used in enterprise Kubernetes/OpenShift; identity spoofing can lead to account takeover and broad app compromise.
CVE-2026-49332
OpenShift oauth-proxy header smuggling allows user identity spoofing.
Is CVE-2026-49332 being exploited?
Not confirmed. CVE-2026-49332 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-49332?
CVE-2026-49332 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-49332?
Yes. A fix has been recorded for CVE-2026-49332. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-49332 affect?
CVE-2026-49332 affects openshift/oauth-proxy, OpenShift clusters using oauth-proxy, Applications behind oauth-proxy, WSGI/PHP frameworks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-49332?
Patch oauth-proxy or block/strip underscore-variant headers at ingress; validate identity headers.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted X_Forwarded_User headers can override authenticated identities, enabling impersonation and privilege escalation in upstream apps.
Immediate action required