Red Hat OpenShift Container Platform 4.12: Server-Side Request Forgery
CVE-2026-50237 is a high-severity server-side request forgery vulnerability in Red Hat OpenShift Container Platform 4.12 from Red Hat, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network 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.47% 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.
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
- 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
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L. Scored by CNA (redhat.com).
Official description
A Server-Side Request Forgery and supply chain flaw was found in the OpenShift Console Helm catalog proxy. A namespace tenant can plant a ProjectHelmChartRepository with an arbitrary URL that the console pod fetches server-side, bypassing tenant egress restrictions. Combined with catalog metadata poisoning and admin-mediated chart installation, this enables privilege escalation.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Server-Side Request Forgery
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
How developers prevent this class of flaw
- If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
- If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2026:54188
- access.redhat.com/errata/RHSA-2026:54206
- access.redhat.com/errata/RHSA-2026:54545
- access.redhat.com/errata/RHSA-2026:54555
- access.redhat.com/errata/RHSA-2026:54583
- access.redhat.com/errata/RHSA-2026:54602
- access.redhat.com/errata/RHSA-2026:54770
- access.redhat.com/errata/RHSA-2026:56789
- access.redhat.com/errata/RHSA-2026:56854
- access.redhat.com/errata/RHSA-2026:56912
- access.redhat.com/errata/RHSA-2026:60023
- access.redhat.com/security/cve/CVE-2026-50237
- bugzilla.redhat.com/show_bug.cgi?id=2484746
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.5 High severity
- 7.6 High severity
Recent Server-Side Request Forgery vulnerabilities
- 8.6 High severity
- 9.1 Critical severity
- 9.3 Critical severity
- 8.3 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.