Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-59869: CWE-407: Inefficient Algorithmic Complexity in nodeca js-yaml

0
High
VulnerabilityCVE-2026-59869cvecve-2026-59869cwe-407
Published: 07/08/2026 (07/08/2026, 15:15:54 UTC)
Source: CVE Database V5
Vendor/Project: nodeca
Product: js-yaml

Description

js-yaml versions from 3.0.0 before 3.15.0 and from 4.0.0 before 4.3.0 have an inefficient algorithmic complexity issue. Parsing YAML documents with a chain of mappings using merge keys can cause quadratic CPU time consumption, leading to potential denial of service. This vulnerability is fixed in versions 3.15.0 and 4.3.0.

CVSS v3.1

Score 7.5high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected software

js-yaml
pkg:npm/js-yaml
Affected versions
>=3.0.0 <3.15.0>=4.0.0 <4.3.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/08/2026, 16:13:33 UTC

Technical Analysis

The js-yaml JavaScript library suffers from a CWE-407 inefficient algorithmic complexity vulnerability in versions >=3.0.0 <3.15.0 and >=4.0.0 <4.3.0. When parsing YAML documents that contain a chain of mappings using merge keys where each mapping merges the previous one, the CPU time required grows quadratically relative to the document size, which itself grows linearly. This can cause excessive CPU consumption during parsing. The issue is resolved in versions 3.15.0 and 4.3.0.

Potential Impact

This vulnerability can cause high CPU usage leading to denial of service conditions when processing specially crafted YAML documents. There is no impact on confidentiality or integrity, only availability is affected.

Mitigation Recommendations

Upgrade js-yaml to version 3.15.0 or later if using the 3.x branch, or to version 4.3.0 or later if using the 4.x branch. No other mitigations are indicated. Patch status is confirmed fixed in these versions.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-07-07T15:41:53.607Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a4e73c2c9d9e3dbe36042b4

Added to database: 07/08/2026, 15:58:58 UTC

Last enriched: 07/08/2026, 16:13:33 UTC

Last updated: 07/08/2026, 21:52:54 UTC

Views: 15

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses