Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/abraxas/loom-adk-a2a-hitl
Authentication & AuthorizationVulnerability AnalysisPenetration TestingAI SecurityLabs & Practice
GitHubabraxas/loom-adk-a2a-hitl

loom-adk-a2a-hitl

On Loom with google-adk 2.13.0, an agent-to-agent tool never waits for the approval check, so the send completes. The same rule still pauses Strands and ordinary ADK functions. v1.9.0 and v1.10.3. Medium 6.5.

View Repository
1 day agoNot yet reviewed
Share

Abraxas Labs - loom-adk-a2a-hitl

loom-adk-a2a-hitl

Loom attaches an approval check to every ADK tool, including the tool that sends a message to another agent. In google-adk 2.13.0 that send tool never calls the check. The message goes out. The same empty or star rule still pauses an ordinary ADK function and the Strands partner tool.

The caller already has invoke on that agent. This is not an anonymous bug, and it is not a shell. The lab counted predicate calls. It did not claim the partner did anything beyond receiving the send.

Class: Approval check bound but never awaited Reach: Remote. In-group invoke on an ADK agent that already has agent-to-agent enabled. google-adk==2.13.0.

Loom v1.9.0 a3050669 and v1.10.3 cc10ab0

IDno CVE yet
ClassADK AgentTool skips the confirmation predicate
ReachRemote, in-group invoke
CWECWE-862
CVSSMedium: 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Productawslabs/loom
Affectedv1.9.0 and v1.10.3, with google-adk[a2a,extensions,mcp]==2.13.0
Authinvoke on that agent
LicenseGNU Affero GPL v3.0
Labloopback Docker on v1.9.0. The dependency pin is unchanged on v1.10.3.

What an attacker can do

PrivilegeMethod / sinkImpactLab-proven or inferred
Have an ordinary ADK function pauseFunctionTool.run_async under an empty or star ruleThe predicate runsLab-proven. Would pause.
Send through the A2A tool without the predicateAgentTool.run_asyncIntegrity. Predicate calls stay 0 and the tool completes.Lab-proven
Have Strands pause on the same rulea2a_partnerContrastLab-proven. Would pause.

Stays closed

AxisMethod / sinkWhy it is closed
IntegrityStrands partner toolThe hook still pauses it
IntegrityADK FunctionToolThe predicate is awaited
IntegrityAnonymous websocketClosed elsewhere. This lab does not reopen it.
IntegrityHTTP payload for StrandsStill includes approval_policies

How I found it

apply_confirmation_to_tools rebinds check_require_confirmation on each tool. The A2A helper returns AgentTool. I stepped through AgentTool.run_async in 2.13.0 and the rebound method is not awaited. FunctionTool.run_async does await it. The pin in agents/adk_agent/requirements.txt is still 2.13.0 on v1.10.3, and this file was not in the v1.10 security commits.

The container ran on v1.9.0.

Lab

python3 loom-adk-a2a-hitl-Abraxas-Labs.py
SUCCESS LOOM-190-ADK-A2A-HITL agenttool-predicate-calls=0 LOOM-190-ADK-A2A-HITL-WITNESS

The fix

Wrap the remote agent in a tool whose run_async awaits check_require_confirmation before the send, or stop using AgentTool until upstream does. A pin bump only helps if the new AgentTool actually awaits the predicate.

References

  • awslabs/loom v1.10.3 cc10ab08573087fa12154f7c8181ffcd985fea88
  • approval.py apply_confirmation_to_tools
  • a2a_client.py
  • CWE-862
  • CVSS 3.1 calculator

License

GNU Affero GPL v3.0. See LICENSE. Loopback lab only. No warranty.

Abraxas Labs [email protected]

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →