Answer in brief
CVE-2026-11572 records a High severity command injection vulnerability in degit has a Command Injection issue. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
Answer in brief
CVE-2026-11572 records a High severity command injection vulnerability in degit has a Command Injection issue. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
Update degit to 2.8.6; degit to 3.3.1 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanCommand Injection describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-11572 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| degitnpm | <2.8.6 | 2.8.6 |
| degitnpm | >=3.0.0,<3.3.1 | 3.3.1 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-11572 records a High severity command injection vulnerability in degit has a Command Injection issue. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for degit, degit.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate degit to 2.8.6; degit to 3.3.1 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanCommand Injection describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-11572 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| degitnpm | <2.8.6 | 2.8.6 |
| degitnpm | >=3.0.0,<3.3.1 | 3.3.1 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-11572 records a High severity command injection vulnerability in degit has a Command Injection issue. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for degit, degit.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardVersions 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.
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.