ZDF
Sign inSign up

Vulnerabilities

Security research · CVE-2026-118773

Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal

Published Oct 30, 2026 · catalog updated Oct 30, 2026 · Glob: AbortSignal cancellation bypass

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-118773. EPSS is 0.35%. Act only if a listed version of Glob: AbortSignal cancellation bypass is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Glob: AbortSignal cancellation bypass).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.35%
Remediation
Version ranges on file
Affected products
npm glob

### Summary In glob 13.0.6, an aborted async walk rejects or emits an error but continues recursively reading directories in the background. The root cause is that abort branches in src/walker.ts call cb() without returning. As a result, callers that rely on signal or AbortSignal.timeout() to bound glob traversal cost can still incur filesystem I/O and CPU work after the request has already been rejected. ### Details This was reproduced on glob v13.0.6 (commit e80cb38ae60d6cbff9e75f39032a994858994d35). The README documents that the signal option cancels the glob walk. However, in src/walker.ts, the following methods call cb() when this.signal?.aborted is true but do not return: - GlobUtil.walkCB() - GlobUtil.walkCB2() - GlobUtil.walkCBSync() - GlobUtil.walkCB2Sync() Example vulnerable pattern: if (this.signal?.aborted) cb() Because execution continues after cb(), the walker still reaches processor.processPatterns(), readdirCB(), and recursive walkCB2() calls. The issue was directly demonstrated against v13.0.6. A source-history review shows the same missing-return pattern is present in tagged releases from v9.0.0 through v13.0.6. The issue affects both glob() and globStream(). Recommended fix: Change each abort branch to return immediately: if (this.signal?.aborted) return cb() ### Proof of concept Environment: - Linux x86_64 - Node.js v22.23.3 - npm 10.9.9 - glob 13.0.6 Reproduction steps: 1. Install the affected package: npm init -y npm install glob@13.0.6 2. Run the attached PoC: node poc/abort-continues-work.mjs The PoC aborts after the first readdir() call, waits briefly, and counts how many more directory reads happen after the promise has already rejected. Observed output on the vulnerable version: { "rejection": "Error: probe-abort", "readdirCalls": 1365, "readdirCallsAtReject": 5, "readdirCallsAfterReject": 1360 } Expected behavior: readdirCallsAfterReject should be 0. A second PoC using AbortSignal.timeout() also reproduces the issue: { "rejection": "Timeo

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm glob>= 9.0.0, <= 14.0.1

How to fix CVE-2026-118773

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-118773. EPSS is 0.35%. Act only if a listed version of Glob: AbortSignal cancellation bypass is installed.

Which versions are affected?

Compare what you have installed with >= 9.0.0, <= 14.0.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption. EPSS 0.35%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 30, 2026 · GitHub Advisory Database

    Detected

    ### Summary In glob 13.0.6, an aborted async walk rejects or emits an error but continues recursively reading directories in the background. The root cause is that abort branches in src/walker.ts call cb() without returning. As a result, callers that rely on signal or AbortSignal.timeout() to bound glob traversal cost can still incur filesystem I/O and CPU work after the request has already been r

  2. Oct 30, 2026 · GitHub Advisory Database

    Updated

    ### Summary In glob 13.0.6, an aborted async walk rejects or emits an error but continues recursively reading directories in the background. The root cause is that abort branches in src/walker.ts call cb() without returning. As a result, callers that rely on signal or AbortSignal.timeout() to bound glob traversal cost can still incur filesystem I/O and CPU work after the request has already been r

Sources

  • CVE.orgVulnerability recordCVE-2026-118773

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-3g3m-2fjr-6pw4

    Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-118773

    In glob 13.0.6, an aborted async walk rejects or emits an error but continues recursively reading directories in the background. The root cause is that abort branches in src/walker.ts call cb() without returning. As a result, callers that rely on signal or AbortSignal.timeout() to bound glob traversal cost can still incur filesystem I/O and CPU work after the request has already been rejected.

    advisories.gitlab.com

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseNov 6, 2026
  • GitLab Advisory DatabaseNov 3, 2026
  • CVE.orgOct 31, 2026