Skip to main content
Mallory
HighVulnerability

CVE-2026-13149: Algorithmic Complexity Denial of Service in brace-expansion

Published Jun 30, 2026 · Updated 16 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS7.7High · v4
EPSS0.36%31st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-13149CWE-407 · Inefficient Algorithmic Complexity

CVE-2026-13149 is an algorithmic complexity vulnerability in the brace-expansion package's expand() function. Crafted expressions containing consecutive non-expanding '{}' groups trigger exponential recursive processing, allowing small inputs to consume excessive CPU and block the Node.js event loop. The max option limits output size rather than recursion work and therefore does not prevent exploitation. Patched releases are available as versions 1.1.16, 2.1.2, and 5.0.7 for the corresponding release branches.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Processing a small attacker-controlled expression can stall the calling thread or process for minutes or effectively indefinitely. In Node.js services, event-loop blocking can prevent unrelated requests and application tasks from completing, causing denial of service. No confidentiality or integrity impact is established.

Mitigation

If you can’t patch tonight, do this now.

Avoid passing untrusted strings to expand() or transitive brace-expansion consumers such as minimatch and glob. Reject or constrain expressions containing repeated non-expanding brace groups. If untrusted expansion is unavoidable, isolate it in a worker or separate process with an externally enforced execution deadline and termination capability. Request-size and rate limits can reduce exposure but are insufficient alone because small inputs can trigger expensive processing. The max option is not an effective mitigation.

Remediation

Patch, then assume compromise.

Upgrade brace-expansion to the patched release for the applicable branch: 1.1.16, 2.1.2, or 5.0.7, or a subsequent fixed release. Update transitive dependency resolutions as necessary to eliminate vulnerable bundled copies. For vendor-packaged applications and operating-system packages, install the applicable vendor security update containing the corrected dependency or backported fix.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-13149 exploited in the wild?
As of Nov 2, 2026, Mallory has no reports of CVE-2026-13149 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-13149?
As of Nov 2, 2026, Mallory has found no public exploit for CVE-2026-13149.
Is there a patch for CVE-2026-13149?
Upgrade brace-expansion to the patched release for the applicable branch: 1.1.16, 2.1.2, or 5.0.7, or a subsequent fixed release. Update transitive dependency resolutions as necessary to eliminate vulnerable bundled copies.
How severe is CVE-2026-13149?
CVE-2026-13149 has a CVSS v4 score of 7.7 (High) and an EPSS score of 0.36% (31st percentile) as of Nov 2, 2026.
Activity feed

Recent activity

37 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+18 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.