How severe is GHSA-q6hv-wcjr-wp8h?

No CVSS score has been assigned to GHSA-q6hv-wcjr-wp8h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q6hv-wcjr-wp8h?

GHSA-q6hv-wcjr-wp8h affects the following packages: github.com/kcp-dev/kcp (Go). Ecosystems affected: Go.

How do I fix GHSA-q6hv-wcjr-wp8h?

Update github.com/kcp-dev/kcp to 0.28.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6hv-wcjr-wp8h is resolved across your whole dependency graph.

How do I detect GHSA-q6hv-wcjr-wp8h in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kcp-dev/kcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q6hv-wcjr-wp8h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-q6hv-wcjr-wp8h actively exploited in the wild?

No public exploit code has been indexed for GHSA-q6hv-wcjr-wp8h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-q6hv-wcjr-wp8h published, and has it been updated?

GHSA-q6hv-wcjr-wp8h was published on September 26, 2025 and was last updated on October 23, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

kcp is missing update validation allows arbitrary LogicalCluster status patches through initializingworkspaces Virtual WorkspaceGHSA-q6hv-wcjr-wp8h

Fix: kcp-dev/kcp#3599

GHSA-q6hv-wcjr-wp8h is a security vulnerability in github.com/kcp-dev/kcp. A fix is available for github.com/kcp-dev/kcp — see the affected versions and patch details below.

Also known asGO-2025-3985

Published

Sep 26, 2025

Updated

Oct 23, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/kcp-dev/kcp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 WorkspaceTypes with initializers that are inherited by other WorkspaceTypes.
Impacts developers using the virtual/framework package 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 initialize verb on WorkspaceType objects (see documentation for details).
Only use trusted WorkspaceType objects.

References

See the pull request (#3599).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/kcp-dev/kcp`	all versions	0.28.3`go get github.com/kcp-dev/kcp@v0.28.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kcp-dev/kcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/kcp-dev/kcp to 0.28.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6hv-wcjr-wp8h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Because UPDATE validation is not being applied, it is possible for an actor with access to an instance of the [initializingworkspaces virtual workspace](https://docs.kcp.io/kcp/latest/concepts/workspaces/workspace-initialization/) 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 e

O3 Security · Impact-Aware SCA

Is GHSA-q6hv-wcjr-wp8h in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works