Policy enforcement bypass via null deployment metadata
Published Jul 31, 2026 · Updated Jul 31, 2026
Metadata verification failure in RHACS 4 allows remote authenticated users to evade deploy-time policy enforcement through a crafted label. The Deployment converter JSON-unmarshals the openshift.io/encoded-deployment-config label and accepts null as replacement identity metadata. Permission to create Kubernetes Deployments is required; the null identity hides violations, prevents Central persistence, and corrupts reporting for that workload.
Summary
What happened
Metadata verification failure in RHACS 4 allows remote authenticated users to evade deploy-time policy enforcement through a crafted label. The Deployment converter JSON-unmarshals the openshift.io/encoded-deployment-config label and accepts null as replacement identity metadata. Permission to create Kubernetes Deployments is required; the null identity hides violations, prevents Central persistence, and corrupts reporting for that workload.
The record
- CVE
- CVE-2026-10079
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Advanced Cluster Security for Kubernetes
- Classifications
- CWE-345, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo