Disclosed weakness · no CVE recorded

AgentScope could interrupt another user’s work during a rejected deletion

AgentScope · AgentScope · session management

First documented disclosure · Review checkpoint

Summary

A request to delete an unowned session could cancel its work and purge its pending messages before the server rejected the request.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reviewed project publications document the weakness. They report no known 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

The deletion paths applied side effects before checking the session or procedure-run owner.

Conditions required

An authenticated caller knows another user’s session or procedure-run identifier.

Potential impact

Another user’s work could stop and queued messages could be lost.

Affected versions and configurations

Pre-fix implementation identified by the project. The full release range is unspecified.

Fix and mitigation status

2.0.12 includes the correction.

Practical next steps

Upgrade to AgentScope 2.0.12 or a later fixed version.

Operating lesson

Check ownership before issuing cancellation or cleanup.

Evidence and limits

The public issue and patch document the prior behavior and its correction. AgentScope lists the fix in its November 16 stable release.

Sources