cve.bz

CVE-2026-120235 ag-ui-protocol ag-ui: Uncontrolled Resource Consumption

2.1 lowEPSS 0.4%

Low (2.1) in ag-ui-protocol ag-ui. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A security vulnerability has been detected in ag-ui-protocol ag-ui up to 0.0.58. Affected is the function parseSSEStream of the file sdks/typescript/packages/client/src/transform/sse.ts of the component SSE Parser. The manipulation leads to resource consumption. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The identifier of the patch is 9e7b2b00bce215bbf731f1e6094f63812527c432. The affected component should be upgraded.

Severity

CVSS 4.0

2.1 low
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

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-120235 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120235?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120235?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120235 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ag-ui-protocol ag-ui0.0.1
ag-ui-protocol ag-ui0.0.2
ag-ui-protocol ag-ui0.0.3
ag-ui-protocol ag-ui0.0.4
ag-ui-protocol ag-ui0.0.5
ag-ui-protocol ag-ui0.0.6
ag-ui-protocol ag-ui0.0.7
ag-ui-protocol ag-ui0.0.8
ag-ui-protocol ag-ui0.0.9
ag-ui-protocol ag-ui0.0.10
ag-ui-protocol ag-ui0.0.11
ag-ui-protocol ag-ui0.0.12
ag-ui-protocol ag-ui0.0.13
ag-ui-protocol ag-ui0.0.14
ag-ui-protocol ag-ui0.0.15
ag-ui-protocol ag-ui0.0.16
ag-ui-protocol ag-ui0.0.17
ag-ui-protocol ag-ui0.0.18
ag-ui-protocol ag-ui0.0.19
ag-ui-protocol ag-ui0.0.20
ag-ui-protocol ag-ui0.0.21
ag-ui-protocol ag-ui0.0.22
ag-ui-protocol ag-ui0.0.23
ag-ui-protocol ag-ui0.0.24
ag-ui-protocol ag-ui0.0.25
ag-ui-protocol ag-ui0.0.26
ag-ui-protocol ag-ui0.0.27
ag-ui-protocol ag-ui0.0.28
ag-ui-protocol ag-ui0.0.29
ag-ui-protocol ag-ui0.0.30
ag-ui-protocol ag-ui0.0.31
ag-ui-protocol ag-ui0.0.32
ag-ui-protocol ag-ui0.0.33
ag-ui-protocol ag-ui0.0.34
ag-ui-protocol ag-ui0.0.35
ag-ui-protocol ag-ui0.0.36
ag-ui-protocol ag-ui0.0.37
ag-ui-protocol ag-ui0.0.38
ag-ui-protocol ag-ui0.0.39
ag-ui-protocol ag-ui0.0.40
ag-ui-protocol ag-ui0.0.41
ag-ui-protocol ag-ui0.0.42
ag-ui-protocol ag-ui0.0.43
ag-ui-protocol ag-ui0.0.44
ag-ui-protocol ag-ui0.0.45
ag-ui-protocol ag-ui0.0.46
ag-ui-protocol ag-ui0.0.47
ag-ui-protocol ag-ui0.0.48
ag-ui-protocol ag-ui0.0.49
ag-ui-protocol ag-ui0.0.50
ag-ui-protocol ag-ui0.0.51
ag-ui-protocol ag-ui0.0.52
ag-ui-protocol ag-ui0.0.53
ag-ui-protocol ag-ui0.0.54
ag-ui-protocol ag-ui0.0.55
ag-ui-protocol ag-ui0.0.56
ag-ui-protocol ag-ui0.0.57
ag-ui-protocol ag-ui0.0.58

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup
  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON