Disclosed weakness · no CVE recorded

AgentScope workspace names could resolve to another workspace’s storage

AgentScope maintainers · AgentScope · Kubernetes workspace

First documented disclosure · Review checkpoint

Summary

Different workspace identifiers could address the same Kubernetes Pod and persistent storage.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The upstream sources document the correction and identify no malicious use.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Lossy normalization produced colliding resource names, and lifecycle operations relied on those names without consistently validating full workspace identity.

Conditions required

Multiple workspaces share a Kubernetes namespace and their identifiers normalize or truncate to the same name.

Potential impact

A session could attach to another workspace’s Pod and read or change its data. Resource lifecycle operations could also affect the wrong workspace.

Affected versions and configurations

The public report identifies the Kubernetes workspace implementation without a complete packaged-version range.

Fix and mitigation status

PR 4029 merged November 17. A packaged fix was not verified.

Practical next steps

Deploy a build containing PR 4029. Verify the ownership of existing Pods and persistent volumes before reusing or deleting them.

Operating lesson

Preserve complete tenant identity when deriving infrastructure names and recheck ownership throughout the resource lifecycle.

Evidence and limits

Issue 4028 was public November 14 at 08:35:19 UTC. PR 4029 merged November 17 at 09:54:09 UTC and preserves compatible legacy resources. Regression evidence uses mocked Kubernetes APIs, with live-cluster validation unperformed locally.

Sources