CVE-2026-56864VulnerabilityPublished 11 Nov 2026

Kubernetes: malicious GOSUMDB was capable of serving arbitrary module content not contained within the transparency

Affects kubernetesSource GCVE Database

Compare

Authoritative record:CVE-2026-56864· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.34.13-r2 soon.

Data as of 11 Nov 2026, 04:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.34.13-r2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade kubernetes to 1.34.13-r2.

Affected software

Product	Affected	Fixed in
CleanStartkubernetes`pkg:apk/cleanstart/kubernetes`Other threats	Affected <1.34.13-r2	Fixed in 1.34.13-r2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Kubernetes to version 1.34.13-r2 or later, where this vulnerability has been fixed. Since a patch is available, applying the official fix is the recommended mitigation. No additional mitigations are specified or required beyond updating to the fixed version.

Description

A security vulnerability in the Kubernetes package allows a malicious GOSUMDB to serve arbitrary module content that is not recorded in the transparency log. This flaw affects Kubernetes versions prior to 1.34.13-r2. The vulnerability has a high severity rating with a CVSS score of 7.5, indicating network exploitable impact with no privileges or user interaction required. A fix is available in version 1.34.13-r2.

Impact

An attacker controlling a malicious GOSUMDB can serve arbitrary module content that is not logged in the transparency log, potentially compromising the integrity of modules used by Kubernetes. This can lead to the use of unauthorized or malicious code in Kubernetes environments, impacting confidentiality. However, there is no direct impact on integrity or availability as per the CVSS vector. No known exploits are reported in the wild at this time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 04:02 UTC

Technical details

References

Community reviews

Related threats