Skip to main content
VulnerabilityPublished

CVE-2026-123562: sveltejs devalue · Uncaught Exception

Affects sveltejs devalueSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 5.9.3 soon.

Data as of 8 Nov 2026, 02:05 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 5.9.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 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 7 Nov 2026.

What to do

Upgrade sveltejs devalue to 5.9.3.

Affected software

ProductAffectedFixed in
sveltejsdevalueAffected
  • >=5.8.0 <5.9.3
Fixed in
  • 5.9.3
npmdevaluepkg:npm/devalueOther threatsAffected
  • >=5.8.0 <5.9.3
Fixed in
  • 5.9.3

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

AI-suggested

Upgrade sveltejs devalue to version 5.9.3 or later, where this issue is fixed. No other mitigation is indicated or required according to the available data.

Description

A vulnerability in sveltejs devalue versions 5.8.0 through before 5.9.3 causes an unhandled promise rejection during asynchronous serialization. This occurs when multiple promises are serialized and a later promise rejects before an earlier one settles, leaving an internal rejection unhandled even if the caller catches the returned promise. An attacker who can influence the timing or failure of these promises may cause the Node.js process to terminate unexpectedly.

References

Community reviews

Loading reviews…