Skip to main content
VulnerabilityPublished Updated

CVE-2026-76827: Red Hat Advanced Cluster Management for Kubernetes 2.11 · Protection Mechanism Failure

Affects Red Hat Advanced Cluster Management for Kubernetes 2.11Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium.

Data as of 16 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.11Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.13Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.14Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.15Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.16Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.17Affected–Fixed in–

AI-suggested

Currently, there is no available mitigation or fix that meets Red Hat Product Security criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat advisories for future updates. Since exploitation requires authenticated managed-cluster credentials, controlling and limiting cluster access is a recommended defensive measure until a fix is released.

Description

A flaw was found in search-indexer. This vulnerability allows a registered and authenticated managed cluster to tamper with or delete another cluster's indexed search data. This is possible because the delta-sync write paths in search-indexer do not properly restrict UPDATE/DELETE operations to data owned by the calling cluster. An attacker could exploit this by crafting specific user identifiers (UIDs) with a different cluster's prefix.

References

Community reviews

Loading reviews…