CVE-2025-29922: kcp allows unauthorized creation and deletion of objects in arbitrary workspaces through APIExport Virtual Workspace
Impact
The APIExport Virtual Workspace can be used to manage objects in workspaces that bind that APIExport for resources defined in the APIExport or specified and accepted via permission claims. This allows an API provider (via their APIExport) scoped down access to workspaces of API consumers to provide their services properly.
The identified vulnerability allows creating or deleting an object via the APIExport VirtualWorkspace in any arbitrary target workspace for pre-existing resources. By design, this should only be allowed when the workspace owner decides to give access to an API provider by creating an APIBinding.
With this vulnerability, it is possible for an attacker to create and delete objects even if none of these requirements are satisfied, i.e. even if there is no APIBinding in that workspace at all or the workspace owner has created an APIBinding, but rejected a permission claim.
Patches
A fix for this issue has been identified and has been published with kcp 0.26.3 and 0.27.0.
Workarounds
For users unable to upgrade to one of the patched versions, the following guidance can be given:
- Minimise the set of people with apiexport/content sub-resource access to APIExport resources. Be aware that this has to apply to all workspaces to be effective. - Filter incoming requests in a reverse proxy with a similar logic as the authorizer added in the referenced pull request.
References
See pull request (https://github.com/kcp-dev/kcp/pull/3338).
Other sources
kcp is a Kubernetes-like control plane for form-factors and use-cases beyond Kubernetes and container workloads. Prior to 0.26.3, the identified vulnerability allows creating or deleting an object via the APIExport VirtualWorkspace in any arbitrary target workspace for pre-existing resources. By design, this should only be allowed when the workspace owner decides to give access to an API provider by creating an APIBinding. With this vulnerability, it is possible for an attacker to create and delete objects even if none of these requirements are satisfied, i.e. even if there is no APIBinding in that workspace at all or the workspace owner has created an APIBinding, but rejected a permission claim. A fix for this issue has been identified and has been published with kcp 0.26.3 and 0.27.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/kcp-dev/kcpto a version that resolves this vulnerability.Fixed in 0.26.3 - Upgrade
Upgrade
kcpto a version that resolves this vulnerability.Fixed in 0.26.3 - Upgrade
Upgrade
kcpto a version that resolves this vulnerability.Fixed in 0.27.0 - Configuration
Minimise the set of people with `apiexport/content` sub-resource access to `APIExport` resources.
Kubernetes API / kcp RBAC (APIExport sub-resource access) Minimise access to apiexport/content sub-resource = only grant apiexport/content sub-resource access to the minimal set of people required for APIExport resources - Configuration
Be aware the fix must apply to all workspaces to be effective.
kcp workspaces Coverage of fix across workspaces = apply fix to all workspaces - Compensating control
Filter incoming requests in a reverse proxy using similar logic as the authorizer added in the referenced pull request (kcp-dev/kcp PR 3338).
Event History
Frequently Asked Questions
What is the severity of CVE-2025-29922?
CVE-2025-29922 is considered a high-severity vulnerability due to unauthorized object creation or deletion via the APIExport VirtualWorkspace.
How do I fix CVE-2025-29922?
To fix CVE-2025-29922, upgrade your kcp software to version 0.26.3 or later.
What systems are affected by CVE-2025-29922?
CVE-2025-29922 affects kcp versions prior to 0.26.3 and versions between 0.26.3 and 0.27.0.
What impact does CVE-2025-29922 have on system security?
CVE-2025-29922 allows malicious users to manipulate objects within any arbitrary target workspace, compromising system integrity.
Is CVE-2025-29922 publicly disclosed?
Yes, CVE-2025-29922 has been publicly disclosed and details are available through various security advisories.