Skip to main content
VulnerabilityPublished

CVE-2026-40608: DayuanJiang next-ai-draw-io · Unthrottled Resource Allocation

Affects DayuanJiang next-ai-draw-ioSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 0.4.15 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.4.15
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 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

Upgrade DayuanJiang next-ai-draw-io to 0.4.15.

Affected software

ProductAffectedFixed in
DayuanJiangnext-ai-draw-ioAffected
  • <0.4.15
Fixed in
  • 0.4.15
npmnext-ai-draw-iopkg:npm/next-ai-draw-ioOther threatsAffected
  • <0.4.15
Fixed in
  • 0.4.15

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

AI-suggested

Upgrade next-ai-draw-io to version 0.4.15 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor's versioning information. No other mitigations are specified or required.

Description

Next AI Draw.io is a next.js web application that integrates AI capabilities with draw.io diagrams. Prior to 0.4.15, the embedded HTTP sidecar contains three POST handlers (/api/state, /api/restore, and /api/history-svg) that process incoming requests by accumulating the entire request body into a JavaScript string without any size limitations. Node.js buffers the entire payload in the V8 heap. Sending a sufficiently large body (e.g., 500 MiB or more) will exhaust the process heap memory, leading to an Out-of-Memory (OOM) error that crashes the MCP server. This vulnerability is fixed in 0.4.15.

References

Community reviews

Loading reviews…