Skip to main content
VulnerabilityPublished Updated

CVE-2026-39429: kcp · Missing Authorization

Affects kcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 0.30.3 or 0.29.3 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.30.3, 0.29.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 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

Upgrade kcp to 0.30.3 or 0.29.3; kcp-dev/kcp to 0.29.3.

Affected software

ProductAffectedFixed in
kcp-devkcpAffected
  • >=0.30.0 <0.30.3
Fixed in
  • 0.30.3
kcp-devkcpAffected
  • <0.29.3
Fixed in
  • 0.29.3
GitHubkcp-dev/kcppkg:github/kcp-dev/kcpOther threatsAffected
  • <0.29.3
Fixed in
  • 0.29.3

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

AI-suggested

This vulnerability is fixed in kcp versions 0.30.3 and 0.29.3. Users should upgrade to at least these versions to remediate the issue. Since the vendor advisory confirms the fix availability, upgrading is the recommended and effective mitigation. No additional mitigations are indicated.

Description

kcp is a Kubernetes-like control plane for form-factors and use-cases beyond Kubernetes and container workloads. Prior to 0.30.3 and 0.29.3, the cache server is directly exposed by the root shard and has no authentication or authorization in place. This allows anyone who can access the root shard to read and write to the cache server. This vulnerability is fixed in 0.30.3 and 0.29.3.

References

Community reviews

Loading reviews…