PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-10079 Red Hat CVE debrief

A flaw in Red Hat Advanced Cluster Security for Kubernetes (RHACS) allows a user with permission to create Deployments to set the openshift.io/encoded-deployment-config label to 'null', causing ACS to treat the workload as having empty UID, name, and labels, and namespace 'default'. This bypasses deploy-time policy detection and enforcement visibility, prevents correct persistence in Central, and breaks violation reporting and compliance correlation for the affected deployment. The issue highlights the importance of proper configuration and monitoring of deployments in Kubernetes environments. Organizations using Red Hat Advanced Cluster Security for Kubernetes should verify their deployments and ensure that the openshift.io/encoded-deployment-config label is properly set to prevent potential bypass of deploy-time policy detection and enforcement. Evidence limits suggest that further verification is needed to confirm affected scope and severity.

Vendor
Red Hat
Product
Red Hat Advanced Cluster Security 4
CVSS
HIGH 8.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-31
Original CVE updated
2026-07-31
Advisory published
2026-07-31
Advisory updated
2026-07-31

Who should care

Organizations using Red Hat Advanced Cluster Security for Kubernetes, administrators and users with permission to create Deployments in Kubernetes environments, and security teams responsible for vulnerability management and compliance should be aware of this vulnerability and take necessary actions to prevent potential bypass of deploy-time policy detection and enforcement. Affected operators and platform teams should review and update security policies to account for this vulnerability and ensure proper configuration of the openshift.io/encoded-deployment-config label.

Technical summary

A flaw in Red Hat Advanced Cluster Security for Kubernetes (RHACS) allows a user with permission to create Deployments to set the openshift.io/encoded-deployment-config label to 'null', causing ACS to treat the workload as having empty UID, name, and labels, and namespace 'default'. This bypasses deploy-time policy detection and enforcement visibility, prevents correct persistence in Central, and breaks violation reporting and compliance correlation for the affected deployment. The issue highlights the importance of proper configuration and monitoring of deployments in Kubernetes environments.

Defensive priority

Organizations using Red Hat Advanced Cluster Security for Kubernetes should verify their deployments and ensure that the openshift.io/encoded-deployment-config label is properly set to prevent potential bypass of deploy-time policy detection and enforcement.

Recommended defensive actions

  • Verify deployments and ensure proper configuration of the openshift.io/encoded-deployment-config label
  • Monitor for potential policy bypass and enforcement visibility issues
  • Review and update security policies to account for this vulnerability
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record indicates a flaw in Red Hat Advanced Cluster Security for Kubernetes (RHACS) that allows a user with permission to create Deployments to bypass deploy-time policy detection and enforcement visibility. The issue is related to the openshift.io/encoded-deployment-config label. Evidence limits suggest that further verification is needed to confirm affected scope and severity. Defenders should verify deployments and ensure proper configuration of the openshift.io/encoded-deployment-config label to prevent potential bypass of deploy-time policy detection and enforcement.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-10079 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-10079

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-10079 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-10079

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.