Skip to main content
VulnerabilityPublished Updated

CVE-2026-61682: kcp · Authentication Bypass by Spoofing

Affects kcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 0.32.2 or 0.31.4 as a priority.

Data as of 2 Nov 2026, 22:58 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 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 2 Nov 2026.

What to do

Upgrade kcp and kcp-dev/kcp to 0.32.2 or 0.31.4.

Affected software

ProductAffectedFixed in
kcp-devkcpAffected
  • >=0.32.0 <0.32.2
Fixed in
  • 0.32.2
kcp-devkcpAffected
  • <0.31.4
Fixed in
  • 0.31.4
GitHubkcp-dev/kcppkg:github/kcp-dev/kcpOther threatsAffected
  • <0.31.4
  • >=0.32.0 <0.32.2
Fixed in
  • 0.31.4
  • 0.32.2

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

AI-suggested

Upgrade affected kcp instances to version 0.31.4 or later, or to version 0.32.2 or later, where the vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed fixed in these versions.

Description

kcp is a Kubernetes-like control plane for form-factors and use-cases beyond Kubernetes and container workloads. Prior to 0.31.4 and 0.32.2, the kcp front-proxy does not remove inbound X-Remote-User, X-Remote-Group, or X-Remote-Extra-* identity headers before forwarding requests to shards. Any authenticated tenant can inject X-Remote-Group: system:masters, authorization.kcp.io/warrant, authentication.kcp.io/scopes, or a group used for per-workspace required-group gating, and the shard trusts these values as authenticated identity assertions. This allows cross-workspace impersonation, authorization bypass, and arbitrary reading, writing, or deletion of resources, secrets, RBAC data, APIExports, APIBindings, and LogicalClusters. This issue is fixed in versions 0.31.4 and 0.32.2.

References

Community reviews

Loading reviews…