GHSA-q6hv-wcjr-wp8h: kcp is missing update validation allows arbitrary LogicalCluster status patches through initializingworkspaces Virtual Workspace
Impact Because UPDATE validation is not being applied, it is possible for an actor with access to an instance of the initializingworkspaces virtual workspace to run arbitrary patches on the status field of LogicalCluster objects while the workspace is initializing. This allows to add or remove any initializers as well as changing the phase of a LogicalCluster (to "Ready" for example).
Published Sep 26, 2025 · Updated Oct 23, 2025
Affected packages
github.com/kcp-dev/kcp
- Ecosystem
- Go
- Affected
- <= 0.28.1
- Fixed in
- 0.28.3
- Check
go list -m github.com/kcp-dev/kcp
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Because UPDATE validation is not being applied, it is possible for an actor with access to an instance of the initializingworkspaces virtual workspace to run arbitrary patches on the status field of LogicalCluster objects while the workspace is initializing.
This allows to add or remove any initializers as well as changing the phase of a LogicalCluster (to "Ready" for example).
As this effectively allows to skip certain initializers or the entire initialization phase, potential integrations with external systems such as billing or security could be affected. Their initializers could be skipped by a WorkspaceType that adds another initializer and grants permissions to the virtual workspace to a rogue or compromised entity.
_Who is impacted?_
- Impacts other owners of
WorkspaceTypeswith initializers that are inherited by otherWorkspaceTypes. - Impacts developers using the
virtual/frameworkpackage to create their own virtualworkspaces if they are using UpdateFuncs in their custom storageWrappers.
Details
The issue occurs because the rest.ValidateObjectUpdateFunc is not being called within the DefaultDynamicDelegatedStoreFuncs. As a result, the intended status overwrite protection from initializers never gets called, allowing arbitrary logicalcluster status patches.
Patches
The problem has been patched in #3599 and is available in kcp 0.28.3 and higher.
Workarounds
- Further limit access to the
initializeverb onWorkspaceTypeobjects (see documentation for details). - Only use trusted
WorkspaceTypeobjects.
References
See the pull request (#3599).
Credited to SimonTheLeg, embik.
References
- https://github.com/kcp-dev/kcp/security/advisories/GHSA-q6hv-wcjr-wp8h
- https://github.com/kcp-dev/kcp/pull/3599
- https://github.com/kcp-dev/kcp/commit/02134a2a51d33652ab288cccd7a13539b59c7584
- https://github.com/kcp-dev/kcp/releases/tag/v0.28.3
- https://pkg.go.dev/vuln/GO-2025-3985
- https://github.com/advisories/GHSA-q6hv-wcjr-wp8h
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-61682
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
critical9.9Sep 18, 2026CVE-2026-39429
kcp's cache server is accessible without authentication or authorization checks
high8.2Apr 8, 2026CVE-2025-29922
kcp allows unauthorized creation and deletion of objects in arbitrary workspaces through APIExport Virtual Workspace
critical9.6Mar 20, 2025GHSA-c7xh-gjv4-4jgv
kcp's impersonation allows access to global administrative groups
medium6.4Dec 11, 2024
