Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.38% for the current model date.
BlackTreeCVE Intelligencekcp-dev · kcp
Official source article: GitHub GHSA-C8W2-FGVX-VHV4 ↗. Check the applicable product and release in the original source.
Critical technical severity; prioritise exposed affected systems while verifying vendor guidance.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Gogithub.com/kcp-dev/kcp | SEMVER: introduced 0; fixed 0.31.4 | 0.31.4 | OSV record ↗aggregator derived · 28 Sep 2026 |
| Gogithub.com/kcp-dev/kcp | SEMVER: introduced 0.32.0; fixed 0.32.2 | 0.32.2 | OSV record ↗aggregator derived · 28 Sep 2026 |
| Gogithub.com/kcp-dev/kcp | SEMVER: introduced 0; fixed 0.31.4; introduced 0.32.0; fixed 0.32.2 | 0.31.4, 0.32.2 | OSV record ↗aggregator derived · 28 Sep 2026 |
| gogithub.com/kcp-dev/kcp | < 0.31.4 | 0.31.4 | GitHub advisory ↗upstream repository advisory · 18 Sep 2026 |
| gogithub.com/kcp-dev/kcp | >= 0.32.0, < 0.32.2 | 0.32.2 | GitHub advisory ↗upstream repository advisory · 18 Sep 2026 |
Critical technical severity; prioritise exposed affected systems while verifying vendor guidance.
Fix not verifiedkcp 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.
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.
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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.
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-290: Authentication Bypass by Spoofing. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 18 Sept 2026 · Last source change 21 Sept 2026, 20:50 UTC · CWE-290 · Authentication Bypass by Spoofing
Core structured fields are present and their contributing authorities are shown above.