Skip to content

CVE-2026-61682 kcp front-proxy does not strip inbound X-Remote-* identity headers, allowing any authenticated client to inject groups/warrants and impersonate system:masters in any workspace

CriticalCVSS 9.9 EPSS 0.38%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: total
Technology
Kubernetes

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.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
kcp-dev github.com/kcp-dev/kcp(Go) < 0.31.4; >= 0.32.0, < 0.32.2 0.31.4, 0.32.2 Fixed
kcp-dev github.com/kcp-dev/kcp = < 0.31.4; = >= 0.32.0, < 0.32.2 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
kcp-dev github.com/kcp-dev/kcp(Go) < 0.31.4 0.31.4
kcp-dev github.com/kcp-dev/kcp(Go) >= 0.32.0, < 0.32.2 0.32.2
kcp-dev github.com/kcp-dev/kcp = < 0.31.4 No fix listed
kcp-dev github.com/kcp-dev/kcp = >= 0.32.0, < 0.32.2 No fix listed

References