Skip to main content
VulnerabilityPublished

CVE-2026-10079: Red Hat Advanced Cluster Security 4 · Insufficient Verification of Data Authenticity

Affects Red Hat Advanced Cluster Security 4Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat Advanced Cluster Security 4Affected–Fixed in–

AI-suggested

Currently, there is no complete mitigation other than installing the update once it is released by Red Hat. Users should monitor Red Hat advisories for the availability of a fix and apply updates promptly when available.

Description

CVE-2026-10079 is a vulnerability in Red Hat Advanced Cluster Security for Kubernetes (RHACS) version 4 where an attacker with permission to create Kubernetes Deployments can manipulate the openshift.io/encoded-deployment-config label to bypass deploy-time policy enforcement and visibility. This causes the system to treat the workload as having empty identity metadata, leading to failure in policy detection, enforcement, and compliance reporting for the affected deployment. No complete mitigation exists other than applying an update once it becomes available.

References

Community reviews

Loading reviews…