Description

A vulnerability was detected in 2FastLabs agent-squad up to 1.1.4. Affected by this vulnerability is the function AgentSquad.routeRequest of the file agent-squad/typescript/src/orchestrator.ts of the component Streaming Agent Response Workflow. The manipulation results in resource consumption. It is possible to launch the attack remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.3",
  "pubDate": "2026-09-03T13:06:21.060Z",
  "pubdate": "2026-09-03T13:06:21.060Z",
  "executiveSummary": "The 2FastLabs agent-squad framework, specifically versions up to 1.1.4, contains a security vulnerability within the Streaming Agent Response Workflow component.\nThis vulnerability is classified as an improper resource management issue that leads to excessive resource consumption.\nThe flaw exists within the AgentSquad.routeRequest function located in agent-squad/typescript/src/orchestrator.ts.\nThe vulnerability allows remote, unauthenticated attackers to trigger a state of resource exhaustion, potentially impacting the availability and stability of the hosting system.\nGiven that the exploit is publicly available and the project maintainers have not addressed the issue despite prior notification, the risk to production environments is elevated.\nAttackers can leverage this vulnerability to induce a Denial of Service (DoS) condition by forcing the application to consume excessive CPU or memory through specifically crafted request payloads.",
  "technicalDetails": "The vulnerability is situated in the orchestrator logic responsible for handling streaming responses within the agent-squad framework. Specifically, the function AgentSquad.routeRequest in agent-squad/typescript/src/orchestrator.ts fails to implement adequate resource limiting or validation mechanisms when processing incoming agent requests.\nThe root cause of this vulnerability lies in the lack of depth or frequency control within the routing logic of the Streaming Agent Response Workflow. When a request is parsed by routeRequest, the system initiates a series of internal operations to handle streaming data. If the input parameters are manipulated, the application may enter an uncontrolled execution loop or allocate recursive resources without sufficient termination criteria or rate limiting.\nThe exploitation process is performed remotely without the need for prior authentication. An attacker can transmit a malicious request to the endpoint managed by the orchestrator. Because the function does not validate the complexity or the expected resource requirements of the incoming stream, the attacker can force the system to saturate its memory or CPU utilization rapidly.\nThe attack flow follows a direct trajectory: 1) The attacker initiates a connection to the network-exposed AgentSquad component. 2) The attacker crafts a request payload designed to maximize resource usage through the routeRequest logic. 3) The function accepts the payload and begins the streaming workflow. 4) Due to the absence of circuit breakers or request timeouts, the orchestrator continues to process the operation until system resources are exhausted or the service crashes.\nThe impact of a successful exploitation is a critical Denial of Service, causing the service to become unresponsive to legitimate users. Since the issue resides in the orchestrator.ts file, which is central to the framework's communication flow, the impact is comprehensive across the agent-squad deployment. The exploitation does not require special privileges, making it highly accessible to remote adversaries. As the exploit is public, the probability of active targeting against systems utilizing agent-squad 1.1.4 and earlier is high."
}