CVE-2026-61682 PUBLISHED

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

Assigner: GitHub_M
Reserved: 10.07.2026 Published: 18.09.2026 Updated: 18.09.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS Score: 9.9

Product Status

Vendor kcp-dev
Product kcp
Versions
  • Version < 0.31.4 is affected
  • Version >= 0.32.0, < 0.32.2 is affected

References

Problem Types

  • CWE-290: Authentication Bypass by Spoofing CWE
  • CWE-302: Authentication Bypass by Assumed-Immutable Data CWE
  • CWE-348: Use of Less Trusted Source CWE