CVE-2026-61682 json
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
published last mo. modified last mo. also EUVD-2026-83043 , GHSA-c8w2-fgvx-vhv4 , GO-2026-6517
- cvss
- 9.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/kcp-dev/kcp 0.31.4, 0.32.2
- kcp kcp 0.31.4, 0.32.2
Is CVE-2026-61682 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/kcp-dev/kcp | <0.31.4 >=0.32.0, <0.32.2 |
0.31.4 0.32.2 |
Affected products
- kcp-dev kcp
Classification
References
-
github.com
/kcp-dev/kcp/commit/7437cdcfec8f927d1a9bf1b2dd1e075d038e27ca
web, patch
- github.com /kcp-dev/kcp/commit/f913ee890fb2fd9fa78e50c43474b078bfb6aeff
-
github.com
/kcp-dev/kcp/security/advisories/GHSA-c8w2-fgvx-vhv4
web, advisory
-
github.com
/kcp-dev/kcp/releases/tag/v0.31.4
web
-
github.com
/kcp-dev/kcp/releases/tag/v0.32.2
web
-
github.com
/kcp-dev/kcp
package
Sources
- CVE List CVE-2026-61682
- GitHub Advisory GHSA-c8w2-fgvx-vhv4
- NVD CVE-2026-61682
- OSV GO-2026-6517
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.