CVE-2026-0933
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSummaryA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCommand injection vulnerability in Wrangler's `pages deploy` command where the `--commit-hash` CLI argument is directly interpolated into a shell command via template literals (e.g., execSync( git show -s --format=%B ${commitHash})), allowing shell metacharacter injection and arbitrary command execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.0.15, < 3.114.17>= 4.0.0, < 4.59.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Wrangler is installedRun `wrangler --version` or `npm list -g wrangler` to see if Wrangler is present on the systemAffected if Wrangler is not installed or the command fails - not applicable to this CVE
-
Identify the installed Wrangler versionRun `wrangler --version` and note the version number (e.g., output like 'Wrangler 3.x.x' or 'Wrangler 4.x.x')Affected if The version output falls within the affected ranges: >= 2.0.15 and < 3.114.17, OR >= 4.0.0 and < 4.59.1
-
Check for pages deploy usage with commit-hashReview CI/CD pipeline configurations, build scripts, and any automation that runs `wrangler pages deploy` with the `--commit-hash` argumentAffected if The `pages deploy` command with `--commit-hash` is being used, and the commit-hash value could be derived from untrusted external input
-
Verify shell metacharacter injection riskExamine where the commit-hash value originates - if it comes from user input, webhooks, or external APIs without sanitization, shell metacharacters could be injectedAffected if The commit-hash value is not validated to exclude shell metacharacters before being passed to the Wrangler CLI
You are affected if you have Wrangler version 2.0.15 through 3.114.16 or 4.0.0 through 4.59.0 installed AND use the `pages deploy` command with the `--commit-hash` argument where the hash value could contain shell metacharacters from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.114.174.59.1
Upgrade Wrangler to v4.59.1+, v3.114.17+, or a supported major version. Review CI/CD pipelines to identify and update all wrangler installations, particularly where commit-hash derives from untrusted external sources.
Wrangler v4 -> v4.59.1 or higher; Wrangler v3 -> v3.114.17 or higher; Wrangler v2 -> migrate to v3 or v4
- 1. Check the current Wrangler version by running: wrangler --version
- 2. For Wrangler v4 users (current version >= 4.0.0 and < 4.59.1): Upgrade to v4.59.1 or higher using: npm install [email protected] or npm install wrangler@latest
- 3. For Wrangler v3 users (current version >= 3.0.0 and < 3.114.17): Upgrade to v3.114.17 or higher using: npm install [email protected] or npm install wrangler@latest
- 4. For Wrangler v2 users (current version >= 2.0.15): Upgrade to a supported major version (v3 or v4) - consider migrating directly to v4 for long-term support
- 5. After upgrade, verify the version with: wrangler --version
- 6. Review CI/CD pipelines and scripts that use --commit-hash parameter to ensure they are not passing untrusted input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0933 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0933 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data