Authenticated workflow interruption via ignored tool restrictions
Published Aug 6, 2026 · Updated Aug 6, 2026
Improper authorization in Mercury Agent 1.1.0 through 1.1.12 allows remote authenticated users to halt sibling sub-agents via web chat. SubAgent.run passes the complete capabilities.getTools() registry into each child loop instead of enforcing delegate_task's allowedTools list, while stop_agent lacks an ownership check. Exploitation requires authenticated dashboard access and model-mediated task delegation; demonstrated impact is enumeration and termination of sibling work, affecting parallel-workflow integrity and availability.
Summary
What happened
Improper authorization in Mercury Agent 1.1.0 through 1.1.12 allows remote authenticated users to halt sibling sub-agents via web chat. SubAgent.run passes the complete capabilities.getTools() registry into each child loop instead of enforcing delegate_task's allowedTools list, while stop_agent lacks an ownership check. Exploitation requires authenticated dashboard access and model-mediated task delegation; demonstrated impact is enumeration and termination of sibling work, affecting parallel-workflow integrity and availability.
The record
- CVE
- CVE-2026-18998
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Cosmic Stack
- Product
- Mercury Agent
- Classifications
- CWE-285, CWE-266
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.1.0
- Affected versionversion=1.1.1
- Affected versionversion=1.1.10
- Affected versionversion=1.1.11
- Affected versionversion=1.1.12
- Affected versionversion=1.1.2
- Affected versionversion=1.1.3
- Affected versionversion=1.1.4
- Affected versionversion=1.1.5
- Affected versionversion=1.1.6
- Affected versionversion=1.1.7
- Affected versionversion=1.1.8
- Affected versionversion=1.1.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- verification_test.py restricted-child orchestration PoCfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo