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-73643: CWE-407: Inefficient Algorithmic Complexity in nodeca js-yaml

0
High
VulnerabilityCVE-2026-73643cvecve-2026-73643cwe-407
Published: 08/13/2026 (08/13/2026, 17:47:30 UTC)
Source: CVE Database V5
Vendor/Project: nodeca
Product: js-yaml

Description

js-yaml versions from 5.0.0 up to but not including 5.2.2 contain an inefficient algorithmic complexity vulnerability. Parsing certain small YAML documents with load() or loadAll() can cause exponential time complexity, leading to high CPU usage and blocking the Node.js event loop. This denial-of-service condition does not require special YAML features like anchors or tags. The issue is fixed in version 5.2.2.

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
>=5.0.0 <5.2.2

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: 08/13/2026, 18:26:31 UTC

Technical Analysis

The js-yaml JavaScript library versions >=5.0.0 <5.2.2 have a vulnerability (CWE-407) where the parser's readFlowCollection function calls parseNode multiple times for nested flow sequences of the same shape, causing exponential parsing time (O(2^n)). This can cause a small YAML input (under 200 bytes) to consume excessive CPU resources, blocking the Node.js event loop and stalling the process. No special YAML constructs are needed to trigger this. The vulnerability is resolved in version 5.2.2.

Potential Impact

Exploitation of this vulnerability results in a denial-of-service condition by causing the Node.js event loop to stall due to excessive CPU consumption during YAML parsing. There is no impact on confidentiality or integrity, only availability is affected.

Mitigation Recommendations

Upgrade js-yaml to version 5.2.2 or later where this issue is fixed. No other mitigations are indicated. Patch status is confirmed fixed in 5.2.2.

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-08-13T14:04:09.603Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a7e08efbf8831d5399b799c

Added to database: 08/13/2026, 18:11:59 UTC

Last enriched: 08/13/2026, 18:26:31 UTC

Last updated: 08/13/2026, 22:03:41 UTC

Views: 7

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