Skip to main content
VulnerabilityPublished Updated

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

Affects nodeca js-yamlSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 5.2.1 : patch nodeca js-yaml soon.

Data as of 20 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.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.2.1, 4.3.1, 3.15.1
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 20 Nov 2026.

What to do

Upgrade js-yaml to 5.2.1, 4.3.1 or 3.15.1; js-yaml to 5.2.1.

Affected software

ProductAffectedFixed in
nodecajs-yamlAffected
  • >=5.0.0 <5.2.1
Fixed in
  • 5.2.1
nodecajs-yamlAffected
  • >=4.0.0 <4.3.1
Fixed in
  • 4.3.1
nodecajs-yamlAffected
  • >=3.0.0 <3.15.1
Fixed in
  • 3.15.1
npmjs-yamlpkg:npm/js-yamlOther threatsAffected
  • >=5.0.0 <5.2.1
Fixed in
  • 5.2.1

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 5.2.1 or later, where this inefficient algorithmic complexity issue is fixed. No other mitigations are indicated. Patch status is confirmed by the version fix information.

Description

js-yaml is a JavaScript YAML parser and dumper. Prior to 3.15.1, 4.3.1, and 5.2.1, YAML11_SCHEMA support for the !!omap tag in src/tag/sequence/omap.ts uses omapTag.addItem() to perform a linear duplicate-key scan on every insertion, causing O(n^2) CPU consumption when yaml.load() parses a crafted ordered-map document. In v3 and v4, !!omap is active and exploitable by default. v5 doesn't use !!omap by default, and the chances of activating it are very low.This issue is fixed in 3.15.1, 4.3.1, and 5.2.1.

References

Community reviews

Loading reviews…