CVE-2026-11572Disclosure

LOWCVSS 7.4 · HIGH

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

  • Patch affected systems immediately
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft

Recommended action window: High priority (within 72h)

NVD 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.

2.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-78CWE-77

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

NONE

Threat summary

  • Public PoC is present in monitored signal
  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • PoC mentioned or linked in 1 signal
  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-06-09: 1PoC Mentioned / Linked · 2026-06-09: 1Patch / Workaround · 2026-06-09: 1Technical Details · 2026-06-09: 106-09
Signal classification1 categories
Disclosure
1100.0%
Full discourse1 post
  • Upwind Security MDR@UpwindMDR
    Disclosure

    🚨High - degit Command Injection (CVE-2026-11572) A command injection flaw in the popular npm scaffolding tool degit lets an attacker run arbitrary OS commands. User-supplied input isn't sanitized before being passed to git shell commands executed via exec() in the _cloneWithGit() and fetchRefs() functions, so a maliciously crafted git repository name breaks out into shell command execution as the process user. Exploitation requires the victim to invoke degit against the attacker-controlled repo name, so the real risk surface is template generators, project bootstrappers, and CI pipelines that feed untrusted repository identifiers into degit. Full confidentiality, integrity, and availability impact, with a Proof-of-Concept already rated in the scoring. Affected: degit < 2.8.6 and 3.0.0 - 3.3.0. 👉Upgrade to degit 2.8.6 or 3.3.1.

    Post summary

    A high‑severity command injection flaw (CVE‑2026‑11572) in the npm tool degit has been disclosed, with a PoC noted and vulnerability details provided; users are advised to upgrade to affected bug‑fixed versions.

    0001070
    210 followersView on X

Explore more