CVE-2026-0933: OS Command Injection in `wrangler pages deploy`
Summary
A command injection vulnerability (CWE-78) has been found to exist in the wrangler pages deploy command. The issue occurs because the --commit-hash parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of --commit-hash to execute arbitrary commands on the system running Wrangler.
Root cause
The commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g., execSync(git show -s --format=%B ${commitHash})). Shell metacharacters are interpreted by the shell, enabling command execution.
Impact
This vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where wrangler pages deploy is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to:
- Run any shell command. - Exfiltrate environment variables. - Compromise the CI runner to install backdoors or modify build artifacts.
Mitigation
- Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. - Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. - Users on Wrangler v2 (EOL) should upgrade to a supported major version.
Credits
Disclosed responsibly by kny4hacker.
Other sources
SummaryA command injection vulnerability (CWE-78) has been found to exist in the wrangler pages deploy command. The issue occurs because the --commit-hash parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of --commit-hash to execute arbitrary commands on the system running Wrangler.
Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g., execSync(git show -s --format=%B ${commitHash})). Shell metacharacters are interpreted by the shell, enabling command execution.
ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where wrangler pages deploy is used in automated pipelines and the
--commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to:
Run any shell command. Exfiltrate environment variables. Compromise the CI runner to install backdoors or modify build artifacts.
Credits Disclosed responsibly by kny4hacker.
Mitigation Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. Users on Wrangler v2 (EOL) should upgrade to a supported major version.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-0933?
CVE-2026-0933 is classified as a critical command injection vulnerability.
How do I fix CVE-2026-0933?
To fix CVE-2026-0933, upgrade to versions of wrangler that are 4.59.1 or higher, or 3.114.17 or higher.
What products are affected by CVE-2026-0933?
CVE-2026-0933 affects npm/wrangler versions below 4.59.1 and 3.114.17.
What is the impact of exploiting CVE-2026-0933?
Exploiting CVE-2026-0933 allows an attacker to execute arbitrary commands on the host system.
When was CVE-2026-0933 discovered?
CVE-2026-0933 was reported in 2026, highlighting its critical nature within the wrangler pages deploy command.