Is github.com/kcp-dev/kcp 0.28 vulnerable?
Go · 4 releases from 0.28.0 to 0.28.3 · latest github.com/kcp-dev/kcp is 0.33.6 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. github.com/kcp-dev/kcp 0.28.3, the last 0.28 release, is affected by 4 known security advisories (1 critical, 1 high, 2 low), including CVE-2026-61682, CVE-2026-39429, CVE-2026-61682. 2 more affect earlier 0.28.x releases. Upgrade to 0.31.4 or later to fix all of them.
go get github.com/kcp-dev/kcp@v0.31.4Is your project on an affected github.com/kcp-dev/kcp?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/kcp-dev/kcp 0.28.3
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 in github.com/kcp-dev/kcp
- Affected
- <0.31.4 · >=0.32.0 <0.32.2
- Fixed in
- 0.31.4, 0.32.2
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
- Affected
- <0.31.4 · >=0.32.0 <0.32.2
- Fixed in
- 0.31.4, 0.32.2
kcp's cache server is accessible without authentication or authorization checks in github.com/kcp-dev/kcp
- Affected
- <0.29.3 · >=0.30.0 <0.30.3
- Fixed in
- 0.29.3, 0.30.3
kcp's cache server is accessible without authentication or authorization checks
- Affected
- >=0.30.0 <0.30.3 · <0.29.3
- Fixed in
- 0.29.3, 0.30.3
Fixed within 0.28.x, affecting earlier releases
kcp is missing update validation allows arbitrary LogicalCluster status patches through initializingworkspaces Virtual Workspace in github.com/kcp-dev/kcp
- Affected
- <0.28.3
- Fixed in
- 0.28.3
kcp is missing update validation allows arbitrary LogicalCluster status patches through initializingworkspaces Virtual Workspace
- Affected
- <0.28.3
- Fixed in
- 0.28.3
Every github.com/kcp-dev/kcp 0.28.x release
Affected: 0.28.0 to 0.28.3. Latest github.com/kcp-dev/kcp: 0.33.6.
| Version | Known advisories |
|---|---|
| github.com/kcp-dev/kcp 0.28.3 | CVE-2026-61682, CVE-2026-61682, CVE-2026-39429, CVE-2026-39429 |
| github.com/kcp-dev/kcp 0.28.2 | CVE-2026-61682, CVE-2026-61682, CVE-2026-39429, CVE-2026-39429, GO-2025-3985, GHSA-q6hv-wcjr-wp8h |
| github.com/kcp-dev/kcp 0.28.1 | CVE-2026-61682, CVE-2026-61682, CVE-2026-39429, CVE-2026-39429, GO-2025-3985, GHSA-q6hv-wcjr-wp8h |
| github.com/kcp-dev/kcp 0.28.0 | CVE-2026-61682, CVE-2026-61682, CVE-2026-39429, CVE-2026-39429, GO-2025-3985, GHSA-q6hv-wcjr-wp8h |
Which of your client projects are still on github.com/kcp-dev/kcp 0.28?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/kcp-dev/kcp version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/kcp-dev/kcp versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.