# CVE-2026-10079: Stackrox: stackrox: deploy-time policy enforcement and visibility bypass via label injection

> Attackers can bypass deploy-time policy enforcement and visibility in Red Hat Advanced Cluster Security by injecting null labels into Kubernetes deployments.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-vq3f-pc8h-pv73

## What is CVE-2026-10079?

CVE-2026-10079 is a high-severity vulnerability in Red Hat Advanced Cluster Security 4, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in Red Hat Advanced Cluster Security for Kubernetes (RHACS). When processing Kubernetes Deployments, ACS replaces deployment identity metadata based on the openshift.io/encoded-deployment-config label. A user with permission to create Deployments can set this 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-10079?


## How do I fix CVE-2026-10079?

No fix has been published for CVE-2026-10079 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10079 being exploited?

There is no known exploitation of CVE-2026-10079 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10079 and fix it if it is affected.

What it is: CVE-2026-10079 is a high-severity vulnerability in Red Hat Advanced Cluster Security 4, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10079 in the wild and no public exploit code.

Affected product: Red Hat Advanced Cluster Security 4. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10079/ (Markdown: https://insights.sbomify.com/CVE-2026-10079/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10079
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10079
- OSV: https://osv.dev/vulnerability/CVE-2026-10079

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10079/
Summaries are generated and may contain mistakes; the official description above is the record.