Security readout for executives and security teams
Plain-English summary
A tenant already permitted to create HelmRelease resources could make an elevated controller deploy resources beyond that tenant’s intended boundaries. Successful abuse could compromise confidentiality, integrity, and availability across the Kubernetes cluster. This is not an unauthenticated entry point, but the resulting privilege escalation is severe.
Executive priority
Treat as an urgent multi-tenant isolation failure. Prioritize internet-facing, shared, or delegated-administration clusters where non-administrators can create HelmRelease resources. Apply the matching Red Hat update promptly, restrict that permission meanwhile, and investigate for prior misuse. Lower exposure may apply where no untrusted identity holds the prerequisite permission.
Technical view
The multicloud-operators-subscription HelmRelease controller renders and applies tenant-supplied charts using its own privileged ServiceAccount. Missing resource-kind and namespace restrictions allow an authorized HelmRelease creator to cause arbitrary cluster-wide resource creation. Red Hat assigns CVSS 3.1 score 9.9 with scope changed and high impact to confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to listed builds of Red Hat Advanced Cluster Management 2.11 and 2.13 through 2.17 using rhacm2/multicluster-operators-subscription-rhel9. Practical risk requires a tenant or identity able to create HelmRelease custom resources. The bundle does not list version 2.12 or establish other products as affected.
Exploitation context
No active exploitation is established: the bundle marks KEV false and provides no cited exploitation report. Abuse requires low privileges rather than no privileges—specifically permission to create HelmRelease resources. In a multi-tenant cluster, that prerequisite may still be accessible to less-trusted users, making rapid remediation important.
Researcher notes
The core issue is a confused-deputy boundary failure consistent with CWE-441: tenant-controlled input is executed through a more privileged controller identity. Assessment should focus on effective RBAC, HelmRelease admission paths, controller ServiceAccount privileges, and resources previously produced by those releases. The supplied evidence does not identify public proof-of-concept code or exploitation in the wild.
Mitigation direction
- Identify affected ACM installations and match their package versions to the listed builds.
- Review the applicable Red Hat erratum and install its vendor-provided security update.
- Until updated, restrict HelmRelease creation to explicitly trusted administrators.
- Review vendor guidance before introducing compensating controller or RBAC changes.
Validation and detection
- Inventory ACM versions and multicluster-operators-subscription-rhel9 package builds across every managed environment.
- Audit RBAC bindings to identify users and service accounts permitted to create HelmRelease resources.
- Review existing HelmRelease objects for unexpected namespaces, resource kinds, ownership, or recent changes.
- Confirm the installed package no longer matches an affected build after remediation.
- Check controller and Kubernetes audit logs for suspicious cluster-wide resource creation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-441: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-67567 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16redhatVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- Source timelineredhat
Made public.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:60386CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:60387CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:60388CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:60389CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:60390CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:60391CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-67567CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2514224CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unintended Proxy or Intermediary ('Confused Deputy')
Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.