Skip to main content
CVE-2026-84375VulnerabilityPublished

Microsoft · js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-84375· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in 5.4.1 : patch Microsoft soon.

Data as of 17 Nov 2026, 10:20 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 5.4.1, 4.3.2, 3.15.2
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 1 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 16 Nov 2026.

What to do

Upgrade js-yaml to 5.4.1, 4.3.2 or 3.15.2.

Affected software

ProductAffectedFixed in
nodecajs-yamlAffected
  • >=5.0.0 <5.4.1
Fixed in
  • 5.4.1
nodecajs-yamlAffected
  • >=4.0.0 <4.3.2
Fixed in
  • 4.3.2
nodecajs-yamlAffected
  • >=3.0.0 <3.15.2
Fixed in
  • 3.15.2

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…