CVE-2026-11572: Degit Command Injection Vulnerability (CVSS 8.8)

Technical summary

The vulnerability resides in degit's _cloneWithGit() and fetchRefs() functions, which invoke git shell commands via the exec() method without adequate input sanitization. An attacker-controlled repository name can include shell metacharacters that break out of the intended git command context, allowing arbitrary command execution. The affected version ranges are before 2.8.6 and from 3.0.0 through 3.3.1. The vulnerability is classified as CWE-77 (Improper Neutralization of Special Elements used in a Command) and CWE-78 (Improper Neutralization of Special Elements used in an OS Command).

Business impact

Organizations using degit in CI/CD pipelines, automated deployment systems, or developer tools face direct risk of system compromise. A successful attack could lead to supply chain contamination, unauthorized code injection into builds, theft of credentials stored on the compromised machine, lateral movement within the network, and loss of confidentiality and integrity. The impact is amplified in shared development environments or CI runners where a single compromise can affect multiple projects or teams.

Affected systems

Degit versions before 2.8.6 and versions 3.0.0 through 3.3.1 are vulnerable. Any system running these versions—whether in development, CI/CD infrastructure, Docker containers, or automated scripts—is at risk. The vulnerability affects all operating systems where degit can execute (Linux, macOS, Windows with appropriate shell support).

Exploitability

Exploitability is relatively straightforward. An attacker crafts a malicious repository name containing shell metacharacters (such as backticks, pipes, or semicolons) and shares it as a seemingly legitimate link. When a user or automated system runs degit with this repository URL, the injected commands execute immediately with no additional user interaction beyond the initial clone request. The attack surface includes any scenario where degit accepts user-controlled or insufficiently validated repository names.

Remediation

Upgrade degit to version 2.8.6 or later for the 2.x branch, or to version 3.3.2 or later for the 3.x branch. If you cannot upgrade immediately, restrict use of degit to trusted repository sources only and avoid running degit with untrusted input. Consider implementing network controls to limit the blast radius of any compromised process.

Patch guidance

Check your current degit version by running `npm list degit` or `yarn list degit`. For npm projects, update with `npm install degit@latest` or specify the safe version in package.json and run `npm install`. For Yarn users, use `yarn upgrade degit`. Verify the installed version meets the security threshold (2.8.6+, or 3.3.2+ for v3 users). Test your build and deployment pipelines after updating to ensure compatibility.

Detection guidance

Monitor for unusual process spawning or command execution originating from degit processes, particularly shell invocations with unexpected arguments. In CI/CD logs, watch for git clone commands with suspicious characters in repository URLs. Log analysis tools should flag any exec() calls from degit that contain shell metacharacters. Additionally, audit your package-lock.json or yarn.lock files to identify if vulnerable versions are pinned in any dependency trees, as degit may be a transitive dependency.

Why prioritize this

With a CVSS 3.1 score of 8.8 (HIGH severity) and a low attack complexity, this vulnerability warrants immediate attention. The requirement for user interaction is minimal—social engineering or automation can easily introduce the attack vector. The potential for complete system compromise combined with common use of degit in build automation makes this a critical remediation priority.

Risk score, explained

The 8.8 CVSS score reflects high impact (Confidentiality, Integrity, and Availability all compromised) and low barriers to exploitation. The attack vector is network-based, requires no privileges, and has low attack complexity. While user interaction is required (the user must invoke degit), the bar for tricking a developer or automaton into running a command is low, especially in open-source or collaborative environments where repository sharing is routine.

Frequently asked questions