Is CVE-2026-10079 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-10079 being exploited in the wild.

How severe is CVE-2026-10079?

High severity, with a CVSS score of 8.5, published 31 July 2026.

Is there a fix for CVE-2026-10079?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-10079 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-10079?

Check whether you run Red Hat Advanced Cluster Security for Kubernetes at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10079: Red Hat Advanced Cluster Security policy bypass via label injection

CVE-2026-10079 · Severity: high · CVSS 8.5 · Published 2026-07-31

A security flaw in Red Hat Advanced Cluster Security (RHACS) allows users with basic deployment permissions to bypass security policy enforcement and monitoring. By applying a specific label to a Kubernetes deployment, an attacker can hide their workloads from the security console, preventing the system from detecting policy violations or maintaining compliance records. This effectively creates a blind spot in the cluster's security oversight, allowing potentially unauthorized or non-compliant containers to run undetected.

Technologies: Red Hat Advanced Cluster Security for Kubernetes. Vendors: Red Hat.

Quick answers

Is CVE-2026-10079 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10079 being exploited in the wild.
How severe is CVE-2026-10079?: High severity, with a CVSS score of 8.5, published 31 July 2026.
Which products and versions are affected?: Red Hat Advanced Cluster Security for Kubernetes 4.
Is there a fix for CVE-2026-10079?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-10079 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-10079?: Check whether you run Red Hat Advanced Cluster Security for Kubernetes at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability classified as Insufficient Verification of Data Authenticity (CWE-345) exists in RHACS during the processing of Kubernetes Deployments. The component responsible for identity metadata replacement reads the 'openshift.io/encoded-deployment-config' label and performs JSON unmarshaling on its value. An attacker with 'create deployment' permissions can set this label to 'null', which is a valid Kubernetes label value but causes the ACS Sensor to treat the workload as having an empty UID, name, and labels, while defaulting the namespace to 'default'. This metadata collision and erasure prevents the Central component from correctly persisting the deployment, effectively bypassing deploy-time policy enforcement and visibility while the container specs remain active.

Affected products

Red Hat Advanced Cluster Security for Kubernetes 4

Timeline

2026-05-29: disclosed: Initial report in Red Hat Bugzilla
2026-07-31: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.