PoC Monitor
← All CVEs
CVE-2026-49329published 1 Sep 2026 15:30 UTCData: JSON · API

Red Hat OpenShift Container Platform 4.13

Openshift/oauth-server: openshift/oauth-server: quadratic-time dos via accept-language header underscore bypass on unauthenticated login endpoints

A flaw was found in openshift/oauth-server. The OAuth login and error page endpoints pass the unauthenticated Accept-Language header to golang.org/x/text/language.ParseAcceptLanguage() without input validation. A bypass of the CVE-2022-32149 mitigation exists: the upstream guard counts only '-' characters but the internal BCP 47 scanner aliases '_' to '-' after the guard check. An unauthenticated attacker can send a crafted Accept-Language header using '_' separators to trigger quadratic-time parsing, consuming excessive CPU and denying authentication to all cluster users.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-407
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Red Hat Red Hat OpenShift Container Platform 4.13

    Fixed in 1793823075

    Red Hat Red Hat OpenShift Container Platform 4.14

      Fixed in 1791839120

      Red Hat Red Hat OpenShift Container Platform 4.15

        Fixed in 1791598539

        Red Hat Red Hat OpenShift Container Platform 4.16

          Fixed in 1792883889

          Red Hat Red Hat OpenShift Container Platform 4.17

            Fixed in 1793907184

            Red Hat Red Hat OpenShift Container Platform 4.18

              Fixed in 1790882323

              Red Hat Red Hat OpenShift Container Platform 4.19

                Fixed in 1790611633

                Red Hat Red Hat OpenShift Container Platform 4.20

                  Fixed in 1790702087

                  Red Hat Red Hat OpenShift Container Platform 4.21

                    Fixed in 1790707106

                    Red Hat Red Hat OpenShift Container Platform 4.22

                      Fixed in 1790713150

                      Mitigation

                      Upgrade Red Hat OpenShift Container Platform 4.13 to 1793823075 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.14 to 1791839120 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.15 to 1791598539 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.16 to 1792883889 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.17 to 1793907184 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.18 to 1790882323 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.19 to 1790611633 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.20 to 1790702087 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.21 to 1790707106 or later.

                      Upgrade Red Hat OpenShift Container Platform 4.22 to 1790713150 or later.

                      Workaround

                      Until an OpenShift update containing the vendor fix is available, place an external WAF or load balancer that terminates TLS in front of the OAuth endpoint. Configure it to reject requests with an Accept-Language header larger than 4 KiB or with more than 32 combined - and _ separators. Rate-limit unauthenticated requests to the OAuth login and error endpoints as an additional defense. The proxy must re-establish TLS to the existing OAuth route, preserve the OAuth hostname/SNI, and validate the backend certificate. Do not disable TLS verification or expose the OAuth service directly. If an external TLS-terminating control cannot be deployed, there is no supported OpenShift router-only mitigation while the OAuth route remains TLS passthrough. Restricting access to the OAuth endpoint to trusted networks can reduce exposure but may affect user access. Upgrade to the first OpenShift release containing the fix as soon as it is available.

                      References

                      5 more

                      Timeline

                      Days relative to CVE publication
                      -2t=0+2+4+6+8CVE published1 Sep 2026 · t = 0

                      No public PoC found yet; not in CISA KEV.

                      PoC repositories

                      Found on GitHub.

                      No PoC repositories found yet.