Live › vulnerability › CVE-2026-120234
The @ag-ui/client TypeScript HTTP transport reads the whole body of any non-2xx response with e.text() with no size cap, then keeps it twice (in the Error message and on error.payload). The reporter measured 46.6 MB of heap growth from a 50 MB error body. The flaw is on the client side: an endpoint the agent connects to, or one an attacker controls, can return a huge error and run the client out of memory. A public PoC is in the issue. The fix, PR #2698, is open and not merged.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-01 16:20 UTC. All times on this page are UTC.
Apps that use the @ag-ui/client HttpAgent (Node or browser) to call agent endpoints. The risk is a hostile or compromised endpoint, or a man-in-the-middle, returning a very large non-2xx body that exhausts the client's memory. The error text also reaches onRunFailed, UIs and logs. Setups where the client only talks to a server you fully control can mostly skip it. The NVD entry says 'ag-ui up to 0.0.58' without naming the package; the issue names the npm package @ag-ui/client.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @ag-ui/client | npm | <= 0.0.58 | – |
npm ls @ag-ui/client (or check your lock file)0.0.58 and earlier are listed as affectedNo fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A weakness has been identified in ag-ui-protocol ag-ui up to 0.0.58. This impacts the function e.text of the component HTTP Transport. Executing a manipulation can lead to resource consumption. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. The pull request to fix this issue awaits acceptance.
This page as .md · .json · in your agent: get_signal("CVE-2026-120234")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.