Command Injection in degit Git Repository Cloning

Versions of the package degit before 2.8.6, from 3.0.0 and before 3.3.1 are vulnerable to Command Injection due to improper sanitisation of user input for git shell commands directly invoked with exec() method by _cloneWithGit() and fetchRefs() functions. An attacker can execute arbitrary operating system commands as the process user by supplying a specially crafted git repository name.

Casky was already ahead

This CVE exploits attack patterns that Casky's 419matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The degit package versions before 2.8.6 and 3.0.0-3.3.1 contain a critical command injection vulnerability in their git cloning functions. By failing to properly sanitize user-supplied git repository names before passing them to shell commands via exec(), attackers can inject arbitrary operating system commands that execute with the privileges of the running process. This vulnerability is particularly dangerous because degit is commonly used in development workflows and CI/CD pipelines to quickly clone and scaffold projects, meaning compromised systems could serve as entry points for supply chain attacks affecting multiple downstream users and organizations.

Casky's security skills leverage Claude's extended reasoning to detect the attack patterns associated with this vulnerability across all three MITRE ATT&CK phases: Initial Access (TA0001) through malicious repository names in requests, Execution (TA0002) through detection of unexpected shell command spawning and process execution anomalies, and Command and Control (TA0043) through monitoring for data exfiltration or lateral movement following successful injection. Practitioners using Casky would see findings highlighting unsanitized input flowing directly into exec() calls, suspicious process spawning from degit operations, and unusual system command execution patterns that deviate from normal repository cloning behavior—enabling them to identify exploitation attempts before arbitrary code runs in their environments.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

419 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-11572.

analyzing-android-malware-with-apktool

malware analysis · medium

Run

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-bootkit-and-rootkit-samples

malware analysis · medium

Run

MITRE ATT&CK Techniques

TA0001 TA0043 TA0002

Investigate the attack patterns behind CVE-2026-11572

Casky has 419 skills that investigate the attack patterns behind CVE-2026-11572. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn