CVE-2026-10079
Label manipulation in RHACS lets creators bypass deployment policy enforcement and visibility.
Is CVE-2026-10079 being exploited?
Not confirmed. CVE-2026-10079 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-10079?
CVE-2026-10079 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-10079?
Not known from our data. No patch reference has been recorded for CVE-2026-10079, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-10079 affect?
CVE-2026-10079 affects Red Hat Advanced Cluster Security for Kubernetes (RHACS), OpenShift / Kubernetes clusters using RHACS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-10079?
Restrict Deployment creation RBAC, audit RHACS/Central logs, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A user able to create Deployments can set a label to 'null' to bypass RHACS policy detection/enforcement, enabling undetected non-compliant workloads and broken compliance reporting.
Patch when possible