Skip to main content
VulnerabilityPublished Updated

CVE-2026-92363: ag-ui · Resource Consumption

Affects ag-uiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ag-ui-protocolag-uiAffected
  • =1.0
Fixed in–
GitHubag-ui-protocol/ag-uipkg:github/ag-ui-protocol/ag-uiOther threatsAffected
  • =1.0
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:ag-ui-protocol:ag-ui:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and applying it is advised to resolve this issue. No additional mitigation steps are specified or required beyond applying the official fix.

Description

A flaw has been found in ag-ui-protocol ag-ui 1.0. Affected is an unknown function of the file src/stream/sse_parser.cpp of the component JSON Parser. Executing a manipulation can lead to resource consumption. The attack may be performed from remote. This patch is called ab6e0bc298996caac2b4b0b3ec0bd8d32a15a186. Applying a patch is advised to resolve this issue.

References

Community reviews

Loading reviews…