CVE-2026-0933: Wrangler Wrangler Affected By OS Command Vulnerability

HIGH
Advisory Identifier: GHSA-36p8-mvp6-cv38
Share
CWE-78
Published
Advisory Summary

CVE-2026-0933 is a HIGH wrangler affected by os command vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Wrangler libraries in the npm ecosystem. The issue involves wrangler affected by os command injection in `wrangler pages deploy`. Remediation is available by upgrading affected packages to version 3.114.17, 4.59.1.

CVE-2026-0933 at a Glance

CVE Identifier CVE-2026-0933
GHSA Identifier GHSA-36p8-mvp6-cv38
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Wrangler
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-0933

To remediate this vulnerability, upgrade all affected Wrangler dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wrangler fixed: 3.114.17 
npm install wrangler@3.114.17
wrangler fixed: 4.59.1 
npm install wrangler@4.59.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls wrangler

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-0933, inspect your project dependencies using npm:

npm ls wrangler

Analyze the terminal output to locate any version of Wrangler in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.114.17), your application is affected.

Note: The npm ls wrangler command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Wrangler, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

**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.

CVE-2026-0933 Affected Wrangler Versions

2 component(s)
Fixed Versions:
3.114.174.59.1
Product / Package Ecosystem Affected Versions Fixed Version
wrangler
npm/wrangler
npm
≥ 2.0.15
< 3.114.17
3.114.17
wrangler
npm/wrangler
npm
≥ 4.0.0
< 4.59.1
4.59.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/cloudflare/workers-sdk/security/advisories/GHSA-36p8-mvp6-cv38
NVD — CVE-2026-0933 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-0933
Security Fix Commit FIX COMMIT
https://github.com/cloudflare/workers-sdk/commit/99b1f328a9afe181b49f1114ed47f15f6d25f0be
Wrangler Source Repository REPOSITORY
https://github.com/cloudflare/workers-sdk
Wrangler Release RELEASE
https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%403.114.17
Wrangler Release RELEASE
https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%404.59.1

Frequently Asked Questions

What is CVE-2026-0933?
CVE-2026-0933 is a security vulnerability in Wrangler involving Wrangler affected by OS Command Injection in `wrangler pages deploy` under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Wrangler versions are affected?
Affected versions include releases prior to 3.114.17, 4.59.1 across affected packages: wrangler.
What version fixes CVE-2026-0933?
Upgrading to 3.114.17, 4.59.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is wrangler affected?
Yes, wrangler is affected in releases prior to 3.114.17, 4.59.1. Upgrade your dependency to 3.114.17, 4.59.1 or later.
What CWE is associated with CVE-2026-0933?
CVE-2026-0933 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check npm dependencies for CVE-2026-0933?
Run the dependency tree command: 'npm ls wrangler'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-36p8-mvp6-cv38",
  "modified" : "2026-01-21T23:00:35Z",
  "published" : "2026-01-21T23:00:35Z",
  "aliases" : [ "CVE-2026-0933" ],
  "summary" : "Wrangler affected by OS Command Injection in `wrangler pages deploy`",
  "details" : "**Summary**\n\nA 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.\n\n**Root cause**\n\nThe `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.\n\n**Impact**\n\nThis 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:\n\n- Run any shell command.\n- Exfiltrate environment variables.\n- Compromise the CI runner to install backdoors or modify build artifacts.\n\n**Mitigation**\n\n- Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. \n- Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. \n- Users on Wrangler v2 (EOL) should upgrade to a supported major version.\n\n**Credits**\n\nDisclosed responsibly by kny4hacker.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "wrangler"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.15"
      }, {
        "fixed" : "3.114.17"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "wrangler"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.59.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/cloudflare/workers-sdk/security/advisories/GHSA-36p8-mvp6-cv38"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-0933"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cloudflare/workers-sdk/commit/99b1f328a9afe181b49f1114ed47f15f6d25f0be"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cloudflare/workers-sdk"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%403.114.17"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%404.59.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-78" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-21T23:00:35Z",
    "nvd_published_at" : null
  }
}