CVE-2026-1784: Ose-cluster-ingress-operator: remote code execution through haproxy configuration injection
The Route OpenShift resource allows to define routes to make pods reachable at a subdomain through HAProxy. It was found that the checks performed on the spec.path YAML stanza in a Route document was insufficient and could allow a controlled injection of the HAProxy configuration.
Other sources
The Route OpenShift resource allows to define routes to make pods reachable at a subdomain through HAProxy. These Routes are managed by the openshift-ingress/router-default pods. One of the features of Routes is their ability to match a URI's path and replace it, this is expressed in the Route by the spec.path and metadata.annotations"[haproxy.router.openshift.io/rewrite-target YAML stanzas in a Route document which are in turn (after various checks and sanitization) used as parameters to a HAProxy configuration template. This configuration template is expressed in plaintext, thus the templating engine cannot automatically escape values to enforce the document structure, escaping has to be performed on the values before the template's evaluation.
By default the Developer role can create Routes to expose their services.
It was found that the checks performed on the Routes spec.path was insufficient and could allow a controlled injection of the HAProxy configuration.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-1784?
The severity of CVE-2026-1784 is classified as high, with a score of 8.8.
What impact does CVE-2026-1784 have?
CVE-2026-1784 allows for remote code execution due to HAProxy configuration injection.
How do I fix CVE-2026-1784?
To mitigate CVE-2026-1784, ensure that your OpenShift routes are properly validated and restrict the HAProxy configuration injection.
What software does CVE-2026-1784 affect?
CVE-2026-1784 affects the Red Hat ose-cluster-ingress-operator.
When was CVE-2026-1784 disclosed?
CVE-2026-1784 was published on June 2, 2026.