CVE-2026-11572: Command Injection in degit
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.
AI Analysis
Technical Summary
The degit package versions prior to 2.8.6 and between 3.0.0 and 3.3.1 contain a command injection vulnerability (CVE-2026-11572) due to insufficient sanitization of user-supplied input in git shell commands executed by the exec() method within the _cloneWithGit() and fetchRefs() functions. This flaw allows attackers to execute arbitrary OS commands as the process user by crafting malicious git repository names. The vulnerability has a CVSS 4.0 score of 8.7, indicating high severity. There is no vendor advisory or patch information currently available, and the vulnerability is not known to be exploited in the wild.
Potential Impact
Successful exploitation enables an unauthenticated attacker to execute arbitrary operating system commands with the privileges of the degit process user. This can lead to system compromise, data theft, or further attacks depending on the environment where degit is used. The high CVSS score reflects the network attack vector, low complexity, no privileges required, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using affected versions of degit with untrusted input, or implement input validation and sanitization controls externally. Monitor official degit repositories and security advisories for updates and patches addressing this vulnerability.
CVE-2026-11572: Command Injection in degit
Description
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.
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The degit package versions prior to 2.8.6 and between 3.0.0 and 3.3.1 contain a command injection vulnerability (CVE-2026-11572) due to insufficient sanitization of user-supplied input in git shell commands executed by the exec() method within the _cloneWithGit() and fetchRefs() functions. This flaw allows attackers to execute arbitrary OS commands as the process user by crafting malicious git repository names. The vulnerability has a CVSS 4.0 score of 8.7, indicating high severity. There is no vendor advisory or patch information currently available, and the vulnerability is not known to be exploited in the wild.
Potential Impact
Successful exploitation enables an unauthenticated attacker to execute arbitrary operating system commands with the privileges of the degit process user. This can lead to system compromise, data theft, or further attacks depending on the environment where degit is used. The high CVSS score reflects the network attack vector, low complexity, no privileges required, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using affected versions of degit with untrusted input, or implement input validation and sanitization controls externally. Monitor official degit repositories and security advisories for updates and patches addressing this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- snyk
- Date Reserved
- 2026-06-08T09:46:19.583Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a27adb3e29bf47b504f94bc
Added to database: 6/9/2026, 6:07:47 AM
Last enriched: 6/9/2026, 6:18:43 AM
Last updated: 6/13/2026, 12:00:29 PM
Views: 21
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.