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 — GHSA-C8W2-FGVX-VHV4
GitHub · GitHub · GHSA-C8W2-FGVX-VHV4
ID
GHSA-C8W2-FGVX-VHV4
GHSA-C8W2-FGVX-VHV4
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
critical
critical
CVSS
9.9
9.9
Summary
# Summary The kcp front-proxy fails to strip client-supplied identity headers before forwarding requests to shards. Any authenticated tenant can inject their own `X-Remote-Group` and `X-Remote-Extra-*` headers, which the shard trusts as a verified identity assertion — allowing a low-privilege user to escalate to cluster administrator (`system:masters`) and read, write, or delete resources in any workspace on the…
Timeline
- Published by source
- 2026-09-18
Risk context
- Reported severity or threat level: critical.
- Reported CVSS score: 9.9 out of 10.
- Review exposure for the affected product or family: go: github.com/kcp-dev/kcp.
Product
go: github.com/kcp-dev/kcp
What to do
General, cautious steps (verify details in the official source):
- Prioritize patching or mitigation immediately (treat as actively risky).
- Identify affected product versions in your inventory and verify whether you are impacted.
- Apply vendor patches/updates or recommended mitigations as soon as available.
- Read the official advisory for exact affected versions and remediation steps.
Official advisory
Evidence and provenance
- Canonical advisory ID
- GHSA-C8W2-FGVX-VHV4
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-09-18
- Last source activity
- 2026-09-18
- Additional identifiers
- CVE-2026-61682
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.