# CVE-2026-50236: Server-side request forgery in Red Hat OpenShift Container Platform 4.14

> Authenticated attackers can exploit SSRF in OpenShift Console webhook helpers to read arbitrary internal endpoints via full response reflection.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 21 Sep 2026
- **Also known as:** CVE-2026-75890, GHSA-c4v8-c9cj-xrmr

## What is CVE-2026-50236?

CVE-2026-50236 is a high-severity server-side request forgery vulnerability in Red Hat OpenShift Container Platform 4.14, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated SSRF flaw was found in the OpenShift Console Dev Console webhook helpers. User-supplied target URLs are fetched server-side without validation, with path neutralization enabling arbitrary endpoint targeting and full response reflection from the console pod's privileged network position.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-50236?


## How do I fix CVE-2026-50236?

No fix has been published for CVE-2026-50236 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-50236 being exploited?

There is no known exploitation of CVE-2026-50236 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50236 and fix it if it is affected.

What it is: CVE-2026-50236 is a high-severity server-side request forgery vulnerability in Red Hat OpenShift Container Platform 4.14, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50236 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Container Platform 4.14. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50236/ (Markdown: https://insights.sbomify.com/CVE-2026-50236/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50236
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50236
- OSV: https://osv.dev/vulnerability/CVE-2026-50236

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50236/
Summaries are generated and may contain mistakes; the official description above is the record.