Red Hat OpenShift Container Platform 4.12: Improper Limitation of a Pathname to a Restricted Directory
CVE-2026-75887 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Red Hat OpenShift Container Platform 4.12 from Red Hat, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.53% 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.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
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.17 | 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 | Red Hat OpenShift Container Platform 4.22 | Not specified in the record | 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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CNA (redhat.com).
Official description
A flaw was found in the OpenShift console. An unauthenticated attacker can exploit a path traversal vulnerability by manipulating the `lng` and `ns` query parameters in the `/locales/resource.json` endpoint. This allows the attacker to read sensitive `*.json` files from the pod filesystem, including plugin manifests and configuration files. Furthermore, this flaw can enable path traversal against registered dynamic-plugin backends.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2026:70587
- access.redhat.com/errata/RHSA-2026:70617
- access.redhat.com/errata/RHSA-2026:70647
- access.redhat.com/errata/RHSA-2026:71447
- access.redhat.com/errata/RHSA-2026:71450
- access.redhat.com/errata/RHSA-2026:71453
- access.redhat.com/errata/RHSA-2026:71454
- access.redhat.com/errata/RHSA-2026:73853
- access.redhat.com/errata/RHSA-2026:73869
- access.redhat.com/errata/RHSA-2026:77321
- access.redhat.com/errata/RHSA-2026:82813
- access.redhat.com/security/cve/CVE-2026-75887
- bugzilla.redhat.com/show_bug.cgi?id=2517889
Other vulnerabilities in Red Hat OpenShift Container Platform 4.12
- 7.7 High severity
- 7.7 High severity
- 9.3 Critical severity
- 7.4 High severity
- 7.5 High severity
- 7.6 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 7.5 High severity
- 9.9 Critical severity
- 7.5 High severity
- 8.6 High severity
Spotted an error? Tell us.