Skip to content
VulniPulse
Sign in
Advisory severityCritical9.9Vendor: HighRed Hat Linux

Critical [CVE-2026-67567] HelmRelease chart applied with controller SA without GVK or namespace restriction

This critical-severity Red Hat Linux advisory covers CVE-2026-67567 affecting Red Hat Advanced Cluster Management for Kubernetes 2.11, Red Hat Advanced Cluster Management for Kubernetes 2.13, Red Hat Advanced Cluster Management for Kubernetes 2.14.

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

CVE-2026-67567 Source published Source updated

VulniPulse record published Record updated

CVE-2026-67567
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 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

A flaw was found in the multicloud-operators-subscription component. This vulnerability allows a tenant, who has the ability to create HelmRelease custom resources (CRs), to bypass existing security controls.

The system's HelmRelease controller processes Helm chart templates using its own elevated ServiceAccount privileges without proper validation. This enables the tenant to deploy arbitrary resources across the entire cluster, leading to a significant security compromise.

A malicious tenant capable of creating HelmRelease custom resources can exploit this to deploy arbitrary resources cluster-wide, bypassing intended namespace and GVK restrictions. This allows for significant privilege escalation within the cluster.

Red Hat severity: Important — CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). Weakness: CWE-441.

Affected Red Hat products: Red Hat Advanced Cluster Management for Kubernetes 2.11; Red Hat Advanced Cluster Management for Kubernetes 2.13; Red Hat Advanced Cluster Management for Kubernetes 2.14; Red Hat Advanced Cluster Management for Kubernetes 2.15; Red Hat Advanced Cluster Management for Kubernetes 2.16; Red Hat Advanced Cluster Management for Kubernetes 2.17.

Red Hat fixing advisory: RHSA-2026:60387, RHSA-2026:60390, RHSA-2026:60388, RHSA-2026:60389, RHSA-2026:60391, RHSA-2026:60386.

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 9 days ago·verify at source

Fixed versions
  • rhacm2/multicluster-operators-subscription-rhel9:1787263584
  • rhacm2/multicluster-operators-subscription-rhel9:1787263693
  • rhacm2/multicluster-operators-subscription-rhel9:1787170830
  • rhacm2/multicluster-operators-subscription-rhel9:1787240030
  • rhacm2/multicluster-operators-subscription-rhel9:1787242321
  • rhacm2/multicluster-operators-subscription-rhel9:1787242108
  • RHSA-2026:60387
  • RHSA-2026:60390
  • RHSA-2026:60388
  • RHSA-2026:60389
  • RHSA-2026:60391
  • RHSA-2026:60386

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

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, restrict the ability of untrusted tenants to create `HelmRelease` custom resources within the cluster. Implement strict Role-Based Access Control (RBAC) policies to limit which users or service accounts can create or modify `HelmRelease` objects. This will prevent unauthorized users from leveraging the controller's elevated privileges for cluster-wide resource deployment.

Official advisory · high-confidence parse· fetched 9 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.