CVE-2026-1784
Ose-cluster-ingress-operator: remote code execution through haproxy configuration injection
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- openshift4/ose-cluster-ingress-operator
Version range not reported
- openshift4/ose-cluster-ingress-operator
Version range not reported
- openshift4/ose-cluster-ingress-operator
Version range not reported
- openshift4/ose-cluster-ingress-rhel9-operator
Version range not reported
- openshift4/ose-cluster-ingress-rhel9-operator
Version range not reported
- openshift4/ose-cluster-ingress-rhel9-operator
Version range not reported
- openshift4/ose-cluster-ingress-rhel9-operator
Version range not reported
- openshift4/ose-cluster-ingress-rhel9-operator
Version range not reported
- openshift4/ose-cluster-ingress-rhel9-operator
Version range not reported