Skip to content
skopnix

NVD published 18 Sep 2026

CVE-2026-61682

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.

Signals

KEV, exploited in the wild
no
EPSS, 30-day forecast
0.4%, 33th percentile (as of 18 Nov 2026)
CVSS, NVD, CRITICAL
9.9
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Internet exposure
not stated

Not in CISA's catalogue as of the last daily pull. Absence is not proof of safety.

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 1 dispatch

  1. GHSA-c8w2-fgvx-vhv4: kcp front-proxy does not strip inbound X-Remote-* identity headers, allowing any authenticated client

Public exploit code none in our sources

No public exploit in the sources we track: GitHub proof-of-concept lists, Metasploit and Exploit-DB. Absence is not proof that none exists.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check