Disclosed weakness · no CVE recorded
Resumed AgentScope tool rounds could exceed the configured iteration budget
AgentScope · AgentScope · agent runtime
First documented disclosure · Review checkpoint
Summary
Some completed external-tool or rejected-approval rounds escaped the agent’s configured maximum number of iterations.
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.
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 iteration counter advanced in the reasoning loop but missed completed rounds that resumed through incoming events.
Conditions required
An agent run uses external execution results or rejected confirmations that repeatedly finish a parked round.
Potential impact
The run could consume additional inference and tool-processing resources beyond the configured bound.
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
Monitor round usage for externally resumed runs until upgrading.
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
- AgentScope original issue
Primary source ·
- AgentScope correction and regression checks
Primary source ·
- AgentScope 2.0.12 release notes
Primary source ·