Skip to content
VulniPulse
Advisory severityHigh7.4Red Hat Linux

High [CVE-2026-50237] Namespace tenant SSRF with egress bypass, catalog poisoning, and admin-mediated supply chain escalation via ProjectHelmChartRepository in OpenShift Console

This high-severity Red Hat Linux advisory covers CVE-2026-50237 affecting Red Hat OpenShift Container Platform 4.12, Red Hat OpenShift Container Platform 4.13, Red Hat OpenShift Container Platform 4.14.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-50237 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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. Red Hat severity: Important — CVSS 7.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L).

Weakness: CWE-918.

Affected Red Hat products: Red Hat OpenShift Container Platform 4.12; Red Hat OpenShift Container Platform 4.13; Red Hat OpenShift Container Platform 4.14; Red Hat OpenShift Container Platform 4.15; Red Hat OpenShift Container Platform 4.16; Red Hat OpenShift Container Platform 4.17; Red Hat OpenShift Container Platform 4.18; Red Hat OpenShift Container Platform 4.19; Red Hat OpenShift Container Platform 4.2; Red Hat OpenShift Container Platform 4.21; Red Hat OpenShift Container Platform 4.22.

Red Hat fixing advisory: RHSA-2026:54206, RHSA-2026:54188, RHSA-2026:56789, RHSA-2026:56912, RHSA-2026:56854, RHSA-2026:60023, RHSA-2026:54545, RHSA-2026:54555, RHSA-2026:54583, RHSA-2026:54602, RHSA-2026:54770.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 29 days ago·verify at source

Fixed versions
  • openshift4/ose-console:1786511587
  • openshift4/ose-console:1786477760
  • openshift4/ose-console:1787056403
  • openshift4/ose-console:1787028559
  • openshift4/ose-console-rhel9:1787054159
  • openshift4/ose-console-rhel9:1787631382
  • openshift4/ose-console-rhel9:1786540776
  • openshift4/ose-console-rhel9:1786486822
  • openshift4/ose-console-rhel9:1786534931
  • openshift4/ose-console-rhel9:1786574043
  • openshift4/ose-console-rhel9:1786607915
  • RHSA-2026:54206
  • RHSA-2026:54188
  • RHSA-2026:56789
  • RHSA-2026:56912
  • RHSA-2026:56854
  • RHSA-2026:60023
  • RHSA-2026:54545
  • RHSA-2026:54555
  • RHSA-2026:54583
  • RHSA-2026:54602
  • RHSA-2026:54770

Official advisory · high-confidence parse· fetched 29 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Review existing ProjectHelmChartRepository resources in tenant namespaces for unexpected URLs using: oc get projecthelmchartrepositories --all-namespaces -o jsonpath='{range .items[*]}{.metadata.namespace}/{.metadata.name}: {.spec.connectionConfig.url}{"\n"}{end}'. Apply NetworkPolicy egress restrictions to the openshift-console namespace (note: requires allow-listing required console egress targets). Administrators should verify chart provenance before installing Helm charts from namespace-scoped repositories. Disable or restrict ProjectHelmChartRepository creation via RBAC if namespace tenants do not require custom Helm repositories.

Official advisory · high-confidence parse· fetched 29 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.