Red Hat OpenShift Container Platform 4.12: External Control of System or Configuration Setting
CVE-2026-1784 is a high-severity external control of system or configuration setting vulnerability in Red Hat OpenShift Container Platform 4.12 from Red Hat, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.19% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat OpenShift Container Platform 4.12 you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on access.redhat.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat OpenShift Container Platform 4.12 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.13 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.14 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.15 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.16 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.18 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.19 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.20 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.21 | Not specified in the record | Not stated |
| Red Hat | Openshift Container Platform | 4.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (redhat.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | CNA (redhat.com) |
| CVSS 3.1 | 8.8 | High | CNA |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: External Control of System or Configuration Setting
One or more system settings or configuration elements can be externally controlled by a user.
How developers prevent this class of flaw
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
- Because setting manipulation covers a diverse set of functions, any attempt at illustrating it will inevitably be incomplete. Rather than searching for a tight-knit relationship between the functions addressed in the setting manipulation category, take a step back and consider the sorts of system values that an attacker should not be allowed to control.
- In general, do not allow user-provided or otherwise untrusted data to control sensitive values. The leverage that an attacker gains by controlling these values is not always immediately obvious, but do not underestimate the creativity of the attacker.
More External Control of System or Configuration Setting vulnerabilities (CWE-15)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- access.redhat.com/errata/RHSA-2026:23241
- access.redhat.com/errata/RHSA-2026:23246
- access.redhat.com/errata/RHSA-2026:25045
- access.redhat.com/errata/RHSA-2026:25182
- access.redhat.com/errata/RHSA-2026:25194
- access.redhat.com/errata/RHSA-2026:26543
- access.redhat.com/errata/RHSA-2026:28893
- access.redhat.com/errata/RHSA-2026:28964
- access.redhat.com/errata/RHSA-2026:70647
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-1784.json
Other vulnerabilities in Red Hat OpenShift Container Platform 4.12
- 7.7 High severity
- 7.7 High severity
- 7.5 High severity
- 9.3 Critical severity
- 7.4 High severity
- 7.5 High severity
Recent External Control of System or Configuration Setting vulnerabilities
- 10.0 Critical severity
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 8.6 High severity
- 8.8 High severity
Spotted an error? Tell us.