Skip to main content
VulnerabilityPublished

CVE-2026-59869: nodeca js-yaml · Inefficient Algorithmic Complexity

Affects nodeca js-yamlSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 4.3.0 or 3.15.0 soon.

Data as of 21 Nov 2026, 17:35 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

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

What to do

Upgrade nodeca js-yaml to 4.3.0 or 3.15.0.

Affected software

ProductAffectedFixed in
nodecajs-yamlAffected
  • >=4.0.0 <4.3.0
Fixed in
  • 4.3.0
nodecajs-yamlAffected
  • >=3.0.0 <3.15.0
Fixed in
  • 3.15.0
npmjs-yamlpkg:npm/js-yamlOther threatsAffected
  • >=3.0.0 <3.15.0
  • >=4.0.0 <4.3.0
Fixed in
  • 3.15.0
  • 4.3.0

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

AI-suggested

Upgrade js-yaml to version 3.15.0 or later, or 4.3.0 or later, where this vulnerability is fixed. No other mitigations are indicated. Patch status is confirmed by the version ranges fixed in the description.

Description

js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 before 3.15.0 and from 4.0.0 before 4.3.0, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in versions 3.15.0 and 4.3.0.

References

Community reviews

Loading reviews…