ag-ui-protocol ag-ui HTTP Transport e.text resource consumption
Affects @ag-ui/client up to 0.0.58 when the server returns a non-2xx HTTP response with a large error body. CVSS scores it 5.3 (medium), and no vendor rating or fix is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The ag-ui-protocol ag-ui software, specifically its HTTP Transport component, is affected by this vulnerability. A remote attacker can manipulate the component's text handling to cause excessive resource consumption.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
Client must receive a non-2xx HTTP response from the server (affects @ag-ui/client up to 0.0.58). Affected package is @ag-ui/client, verified against npm release 0.0.58.Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ag-ui-protocol ag-ui
0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15, 0.0.16, 0.0.17, 0.0.18, 0.0.19, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24, 0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.0.30, and 28 more
Evidence 7
- Advisory
- Advisory
- Advisory
- Advisory
- Patch
- Exploit
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120234
What does this mean?
On any non-2xx HTTP response, the ag-ui HTTP transport reads the entire error body into memory. A single large error body can run the client out of memory, and the attacker-controlled text is passed through onRunFailed into application UIs and logs.Source: github.com
Am I affected, and how do I check?
The affected package is @ag-ui/client, verified against npm release 0.0.58, and the issue applies to versions up to and including 0.0.58. To check a project, look at the installed @ag-ui/client version in package.json or the output of npm ls @ag-ui/client.Source: github.com
What should I do about it?
The checked facts name no fixed version and no workaround, so no upgrade target can be given here. Check the project's advisory or the npm release history for a version newer than 0.0.58.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data