Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-75885 – Unauthenticated SSRF & DoS – Red Hat OpenShift Container Platform 4 (Console)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-75885 is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability (CWE-918) in the Red Hat OpenShift Container Platform 4 web console. Unauthenticated attackers can abuse the console’s /api/devfile/ endpoints to force the console backend to make arbitrary outbound HTTP requests to internal-only services, and can also trigger unbounded memory growth leading to denial of service. Red Hat rates this vulnerability as Important with a CVSS v3.1 base score of 9.3.

Technical details

  • Root cause: The OpenShift console backend (bridge) registers the /api/devfile/ and /api/devfile/samples/ routes directly with handleFunc() instead of wrapping them in the standard authHandler/authHandlerWithUser middleware used by every other /api/* route, leaving them completely unauthenticated.
  • SSRF trigger: The devfile parser accepts untrusted, attacker-supplied JSON payloads and resolves parent.uri, Kubernetes URIs, and remote plugin references by making outbound HTTP requests on behalf of the console, without validating the destination. This allows an attacker to point requests at internal-only services (e.g., cloud metadata endpoints, etcd, kubelets) that are otherwise unreachable from outside the cluster.
  • Information disclosure: Partial response bodies from these internal requests can be reflected back to the attacker via parser error messages, potentially leaking sensitive internal data.
  • Resource exhaustion / DoS: The endpoints also accept large POST bodies without a Content-Length limit, allowing an attacker to send oversized, unbounded requests that cause excessive memory consumption on the console backend.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: High confidentiality impact from SSRF-enabled access to internal network services (potential firewall bypass and internal network reconnaissance/port scanning via the console as a proxy), plus low availability impact from memory-exhaustion DoS against the console component.

Affected software

  • Red Hat OpenShift Container Platform 4 — openshift4/ose-console package
  • Red Hat OpenShift Container Platform 4 — openshift4/ose-console-rhel9 package

Severity

  • CVSS v3.1 Base Score: 9.3 (Critical, rated "Important" by Red Hat)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Mitigation and recommended actions

  • Immediate: As of this writing, Red Hat states that "no mitigation is currently available meeting Red Hat’s security criteria," and no fixed package version has been published for this CVE. Security teams should monitor Red Hat’s advisory (access.redhat.com/security/cve/CVE-2026-75885) and apply the corresponding errata as soon as a fixed ose-console/ose-console-rhel9 build is released.
  • Network mitigations (until a patch is available):
    • Restrict or proxy access to the OpenShift console API so that unauthenticated requests to /api/devfile/ and /api/devfile/samples/ are blocked at the ingress/load-balancer or WAF layer.
    • Ensure internal-only services (cloud metadata endpoints, etcd, kubelet APIs, etc.) enforce their own authentication/network segmentation so they cannot be reached even if the console is used as an SSRF proxy.
    • Enforce request body size limits at the reverse proxy/ingress in front of the console to reduce exposure to the resource-exhaustion vector.
    • Monitor console pod logs and outbound network traffic for anomalous requests to internal-only hosts or unusually large unauthenticated POST requests to the console.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge