What is CVE-2026-75885?

CVE-2026-75885 is Openshift/console: openshift/console: unauthenticated ssrf and resource exhaustion via devfile parser endpoint. The supplied enrichment data classifies it as SSRF mapped to CWE-918 Server-Side Request Forgery (SSRF).

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-75885. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-75885 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-75885. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, cloud metadata access logs, egress proxy logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-75885 using CVSS 9.3, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalSSRF

CVE-2026-75885

CVE-2026-75885 — Openshift/console: openshift/console: unauthenticated ssrf and resource exhaustion via devfile parser endpoint

A flaw was found in the OpenShift console. Unauthenticated access to the `/api/devfile/` and `/api/devfile/samples/` endpoints allows a remote attacker to send crafted devfile payloads. This can lead to Server-Side Request Forgery (SSRF), where the console pod makes requests to internal services and reflects partial responses to the attacker. Additionally, by sending repeated large requests without a specified content length, an attacker can cause unbounded memory growth, leading to a Denial of Service (DoS).

Published Sep 18, 2026Updated Sep 18, 2026Sources: NVD, Red Hat (CNA), GitHub, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

Red Hat

2 products listed

CVSS base

9.3

critical

Remediation

The vendor's own words where we have them.

Upgrade Red Hat OpenShift Container Platform 4 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2026-75885

fixed0affected2not affected0

workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, appli…

none_available: Affected

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Red Hat	Red Hat OpenShift Container Platform 4	—	Vulnerable
Red Hat	Red Hat OpenShift Container Platform 4	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

High

Integrity

None

Scope

Changed

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.3	CVSS 3.1	critical	3.9	4.7	NVD, Red Hat (CNA), Red Hat (VEX)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Weakness & attack patterns

CWE-918Server-Side Request Forgery (SSRF)

Inferred from the weakness class — not observed against this CVE.

CAPEC-664 · Server Side Request Forgery

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /api/devfile/, /api/devfile/samples/.
Prioritize edge telemetry for network-reachable Red Hat OpenShift Container Platform 4.

web/proxy/WAF logsapplication logsnetwork IDS/IPScloud metadata access logsegress proxy logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.3 (AV:N)
Sep 18, 2026 · NVD
Initial · CVE published
Sep 18, 2026 · NVD
Reported · Made public.
Sep 18, 2026 · Red Hat
2025
Reported to Red Hat.
Nov 7, 2025 · Red Hat

References

4 on the record

access.redhat.com/security/cve/CVE-2026-75885
Vendor Advisory
bugzilla.redhat.com/show_bug.cgi?id=2517885
Vendor Advisory
www.cve.org/CVERecord?id=CVE-2026-75885
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-75885
NVD

Elsewhere on this site

Red Hatevery CVE for this vendor
SSRFsame class
CWE-918other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-75885 is Openshift/console: openshift/console: unauthenticated ssrf and resource exhaustion via devfile parser endpoint, a critical vulnerability affecting Red Hat OpenShift Container Platform 4 from Red Hat. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-75885. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-75885. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.