Live › vulnerability › CVE-2026-117505
Go to dashboarda2a-java, the Java SDK for the Agent2Agent protocol, has a flaw in the ChildQueue offer function that a remote caller can trigger by manipulating input. An attacker can drive resource consumption on the affected service, which can degrade or deny availability.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 15:32 UTC. All times on this page are UTC.
Teams running a2a-java or earlier in a service that accepts remote A2A requests are exposed, because the flaw can be triggered remotely. Projects that do not use a2a-java, or that run it only internally with no remote access, are less exposed. The sources do not say which request paths reach the vulnerable ChildQueue code.
1.2.0.FinalNo product ranges from the sources yet.
1.2.0.Final or earlier.1.3.0.Final or later, which the advisory says resolves the issue (patch commit be663f806efcfdddd2805d214fae4998379ac5f2).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A security flaw has been discovered in a2aproject a2a-java up to 1.2.0.Final. The impacted element is the function queue.offer of the component ChildQueue. Performing a manipulation results in resource consumption. The attack can be initiated remotely. Upgrading to version 1.3.0.Final is sufficient to resolve this issue. The patch is named be663f806efcfdddd2805d214fae4998379ac5f2. It is advisable to upgrade the affected component.
This page as .md · .json · in your agent: get_signal("CVE-2026-117505")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.