---
id: "CVE-2026-118773"
kind: "vulnerability"
aliases: ["CVE-2026-118773"]
title: "glob: abort handling keeps traversing after cancellation, stacking filesystem work"
severity: "medium"
cvss: 6.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["glob", "javascript", "node", "package", "self-hosted"]
not_affected_if: ["fixed-patterns", "glob-below-9.0.0", "no-abort-signal"]
published_at: "2026-10-29T19:17:19+00:00"
first_seen_at: "2026-10-29T19:26:47+00:00"
updated_at: "2026-10-29T19:27:29+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-118773", "first_seen_at": "2026-10-29T19:26:47+00:00"}]
---

# glob: abort handling keeps traversing after cancellation, stacking filesystem work

The glob package, versions 9.0.0 through 14.0.2, keeps running directory traversal after an AbortSignal fires, because the abort branches invoke callbacks without returning. An attacker who can supply patterns or trigger repeated timed-out requests can stack background filesystem and CPU work, degrading service availability.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed glob version with `npm ls glob` in each project.
- Look for applications that pass attacker-influenced patterns to `glob()` or `globStream()` and use AbortSignal or AbortSignal.timeout() as a traversal budget.

## Fix

- glob: `14.0.2`

## Timeline

- 2026-10-29T19:26:47+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-118773

## From the sources

Glob matches files using patterns the shell uses. From 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke the callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget. Repeated timed-out requests can stack background filesystem operations and CPU work, degrading worker throughput or service availability; no confidentiality or integrity impact was observed. This issue is fixed in 14.0.2.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_
