Bug 2484746 (CVE-2026-50237)

Summary: CVE-2026-50237 openshift/console: Namespace tenant SSRF with egress bypass, catalog poisoning, and admin-mediated supply chain escalation via ProjectHelmChartRepository in OpenShift Console
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
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.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Deadline: 2026-08-11   

Description OSIDB Bzimport 2026-06-04 12:12:16 UTC 
A flaw was found in the OpenShift Console Helm catalog proxy. A tenant with namespace edit permissions can create a ProjectHelmChartRepository (PHCR) resource with an arbitrary spec.connectionConfig.url. When any user browses the namespace Helm catalog, the openshift-console pod fetches that URL server-side without URL validation or private-range blocking. The tenant can supply custom CA certificates, TLS client certificates, and basic authentication credentials from namespace-scoped ConfigMaps and Secrets that the console pod consumes for the outbound request, enabling the console to present attacker-controlled authentication identities. The console pod fetch bypasses tenant namespace egress NetworkPolicy restrictions. Tenant-controlled chart metadata with trust-spoofed annotations is preserved in the aggregated catalog response visible to other users. Additionally, if a cluster-admin installs a tenant-planted chart through the console UI, cluster-scoped resources (ClusterRole, ClusterRoleBinding) are created under admin authority, enabling admin-mediated privilege escalation. Same-namespace Helm catalog availability can be degraded by planting multiple slow-responding PHCRs.