Security readout for executives and security teams
Plain-English summary
A namespace-level user may abuse ClusterCurator creation to receive cluster-wide privileges. This could expose or alter secrets, disrupt cluster operations, and delete hosted clusters or node pools. The flaw crosses an intended security boundary, so affected Red Hat Multicluster Engine environments require urgent review.
Executive priority
Prioritize immediate exposure assessment and access restriction. A successful attack could convert limited tenant access into cluster-wide control, creating confidentiality, integrity, and availability risk. Accelerate vendor-directed remediation once applicable versions and fixes are confirmed.
Technical view
CVE-2026-73269 is a CWE-269 privilege-escalation flaw in cluster-curator-controller. A low-privileged user who can create a specially named ClusterCurator resource can trigger a cluster-scoped ClusterRoleBinding for a namespace-local service account. The resulting permissions reportedly include cluster-wide secret access and administrative actions. CVSS 3.1 is 9.9.
Likely exposure
Potential exposure exists where Red Hat Multicluster Engine deploys the affected cluster-curator-controller package and namespace-local identities can create ClusterCurator resources. The supplied record provides no affected-version range, so package and version inventory must be compared with current Red Hat guidance.
Exploitation context
The attack requires existing low-privileged access and permission to create the relevant resource, but needs no user interaction and has low stated complexity. The supplied sources do not establish active exploitation, and the provided KEV indicator is false. Treat this as a serious privilege-escalation path, not an unauthenticated compromise.
Researcher notes
The security boundary failure is the controller's creation of a cluster-scoped binding from tenant-controlled input. The supplied description mentions a naming convention but provides no safe validation signature, affected versions, patch, or mitigation. Confirm those details through Red Hat before declaring systems fixed or unaffected.
Mitigation direction
- Check Red Hat guidance for patched releases or approved mitigations; none are identified in the supplied material.
- Temporarily restrict untrusted namespace identities from creating or modifying ClusterCurator resources.
- Investigate unauthorized controller-created ClusterRoleBindings and remediate them after confirming operational dependencies.
- Rotate affected credentials if evidence shows unauthorized cluster-wide secret access.
Validation and detection
- Inventory Multicluster Engine deployments and record cluster-curator-controller package versions.
- Review which namespace-local users and service accounts can create ClusterCurator resources.
- Audit cluster-scoped role bindings connecting namespace service accounts to broad privileges.
- Review logs for suspicious ClusterCurator creation, binding changes, secret access, or destructive cluster actions.
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-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-73269 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
- https://access.redhat.com/security/cve/CVE-2026-73269CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2514220CVE 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.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.