High [CVE-2026-66798] Restore.spec.hooks passed verbatim to Velero Restore — arbitrary command execution in restored pods
This high-severity Red Hat Linux advisory covers CVE-2026-66798 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.
VulniPulse record published Record updated
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.
Summary
Use after free in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network. A flaw was found in cluster-backup-operator.
A namespace administrator in open-cluster-management-backup can create a Restore Custom Resource (CR) with malicious hooks. These hooks allow the execution of arbitrary commands within any matching restored pod, leading to the exfiltration of ServiceAccount tokens.
This bypasses normal access controls, granting the attacker unauthorized execution access to pods and their associated Service Accounts. This vulnerability is rated as Important because an authenticated user with administrative access to the backup namespace can achieve cluster-wide privilege escalation.
By defining custom restore operations containing uninspected execution hooks, an attacker circumvents standard pod execution controls across target restored workloads. This bypass enables unauthorized command execution and credential exfiltration across different namespaces, exceeding the boundary of the backup operator namespace.
Red Hat severity: Important — CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-77.
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 4 hours ago·verify at source
- rhacm2/cluster-backup-rhel9-operator:1787684668
- rhacm2/cluster-backup-rhel9-operator:1787259060
- rhacm2/cluster-backup-rhel9-operator:1787183178
- rhacm2/cluster-backup-rhel9-operator:1787238500
- rhacm2/cluster-backup-rhel9-operator:1787183176
- rhacm2/cluster-backup-rhel9-operator:1787227576
- RHSA-2026:60387
- RHSA-2026:60390
- RHSA-2026:60388
- RHSA-2026:60389
- RHSA-2026:60391
- RHSA-2026:60386
Official advisory · high-confidence parse· fetched 4 hours ago·verify at source
Mitigation checklist
- To mitigate this issue, ensure that only highly trusted administrators are granted `namespace-admin` privileges within the `open-cluster-management-backup` namespace. This restricts the ability to create or modify `Restore` Custom Resources with malicious hooks, thereby preventing arbitrary command execution in restored pods.
Official advisory · high-confidence parse· fetched 4 hours 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.