LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0933: OS Command Injection in `wrangler pages deploy`

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.

HighCVSS 7.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-0933 is a command injection flaw in Cloudflare Wrangler’s `pages deploy` workflow. If an attacker can control the `--commit-hash` value used by automation, they may run commands on the CI/CD runner. This is most urgent for teams deploying Cloudflare Pages from pipelines using externally supplied commit metadata.

Executive priority

Prioritize remediation for production deployment pipelines and shared CI runners. The business risk is highest where compromised pipelines could expose secrets or alter deployed Cloudflare Pages artifacts.

Technical view

The issue is caused by `--commit-hash` being interpolated into a shell command without proper validation or sanitization. Shell metacharacters may be interpreted, enabling arbitrary command execution. The source description identifies CWE-78 behavior, while the provided CWE metadata lists CWE-20.

Likely exposure

Exposure is concentrated in CI/CD environments running `wrangler pages deploy` where `--commit-hash` is populated from external or untrusted sources. Local manual use is less exposed unless attackers can influence that argument.

Exploitation context

The source says exploitation is generally hard because attacker control of `--commit-hash` is required. No KEV listing or provided source indicates active exploitation. Potential impact includes command execution, environment variable exposure, CI runner compromise, and modified build artifacts.

Researcher notes

Affected data in the source lists Cloudflare Wrangler v3.0.0, v4.0.0, and v2.0.15+, with fixes stated for v3.114.17+ and v4.59.1+. Version-range precision is incomplete; validate against Cloudflare’s repository or advisory materials.

Mitigation direction

  • Upgrade Wrangler v4 users to v4.59.1 or higher.
  • Upgrade Wrangler v3 users to v3.114.17 or higher.
  • Move Wrangler v2 users to a supported major version.
  • Ensure `--commit-hash` is not sourced from untrusted input.
  • Review vendor guidance for any additional release notes or advisories.

Validation and detection

  • Inventory Wrangler versions used by developers and CI/CD runners.
  • Find pipelines invoking `wrangler pages deploy`.
  • Check whether `--commit-hash` is set automatically from external inputs.
  • Confirm fixed Wrangler versions are installed in build images and runners.
  • Review recent pipeline logs and secrets exposure if untrusted input was possible.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0933 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.7 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

7.7High
CVSS 4.0 vector shape for CVE-2026-0933Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CloudflareWranglerWrangler, v3.0.0, v4.0.0, v2.0.15+unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.