Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal

Why it is Yellow

• CVSS 6.3 medium
• Public exploit or proof of concept referenced
• On your watchlist: npm

Affected packages

References

• https://github.com/isaacs/node-glob/commit/4682e8c9babee1b385202ede36389634e12076d7
• https://github.com/isaacs/node-glob/releases/tag/v14.0.2
• https://github.com/isaacs/node-glob/security/advisories/GHSA-3g3m-2fjr-6pw4
• https://github.com/advisories/GHSA-3g3m-2fjr-6pw4
• https://nvd.nist.gov/vuln/detail/CVE-2026-118773
• https://github.com/advisories/GHSA-3g3m-2fjr-6pw4

Original description

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.