ag-ui-protocol ag-ui Interrupt expiry index.ts isInterruptExpired resource consumption
Affects @ag-ui/client 0.0.58 when a server run finishes with interrupt outcomes that omit expiresAt. No vendor severity rating is given, and no 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 TypeScript client library's interrupt expiry handling, is affected by this vulnerability. A remote attacker could potentially cause excessive resource consumption in the affected component.
Read the original description
A flaw has been found in ag-ui-protocol ag-ui up to 0.0.58. Affected by this issue is the function isInterruptExpired of the file sdks/typescript/packages/client/src/interrupts/index.ts of the component Interrupt expiry. This manipulation causes resource consumption. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.
What to do
Check whether your setup matches what the bug needs.
Affected package is @ag-ui/client version 0.0.58 A server run finishes with interrupt outcomes that omit expiresAtApply 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-120237
What does this mean?
When a server run finishes with interrupt outcomes that have no expiry time, a single RUN_FINISHED message can permanently stall the client's run handling for that thread. There is no automatic recovery, so the agent session locks up.Source: github.com
Am I affected, and how do I check?
The affected package is @ag-ui/client version 0.0.58, in runs where interrupt outcomes omit expiresAt. To check the installed version, use the package manager's list command for @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. Check the advisory for an updated release before relying on any version.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