Loading story…
A high-severity flaw in Dulwich tracked as CVE-2026-42305 allows arbitrary file write and potential remote code execution on Windows when a user clones, fetches, or checks out a malicious Git repository. The bug affects versions 0.10.0 through 1.2.4 and stems from improper validation of tree entry names that Windows interprets as path syntax, including backslashes, NTFS alternate data stream markers, and NTFS 8.3 short-name aliases tied to .git. A crafted repository can write files outside the work tree or place executable content such as .git\hooks\pre-commit.exe inside the victim’s Git metadata, which Git for Windows may later execute in the user’s context.
The project released Dulwich 1.2.5 to fix the issue, correcting mishandled core.protectNTFS and core.protectHFS configuration names, enabling core.protectNTFS by default on all platforms, and tightening checks to block dangerous names including reserved Windows devices like CON, NUL, COM1, and LPT1. Release notes say the update also addresses other security bugs, including unsafe submodule path handling, shell command injection in ProcessMergeDriver, unsafe patch filename generation, and improper receive.maxInputSize enforcement. Maintainers said there is no effective workaround short of upgrading, and warned that even POSIX users can unknowingly propagate malicious trees to Windows users through pushes or republished repositories.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
On 2026-06-10, CVE-2026-42305 was published describing the Dulwich Windows arbitrary file write vulnerability affecting versions before 1.2.5. The entry noted there was no effective pre-patch workaround and advised users to upgrade.
On 2026-05-28, a GitHub security advisory disclosed a vulnerability in Dulwich versions 0.10.0 through 1.2.4 that can allow arbitrary file write and possible remote code execution on Windows when cloning, fetching, or checking out a malicious repository. The advisory said version 1.2.5 fixes the issue by correcting configuration handling, enabling core.protectNTFS by default, and tightening NTFS path validation.
Dulwich released version 1.2.5 as a security update on 2026-05-28 and urged users to upgrade. The release fixes multiple vulnerabilities, including the Windows NTFS-hostile tree entry flaw later tracked as CVE-2026-42305.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
5 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A high-severity vulnerability tracked as **CVE-2025-48384** affects Git’s handling of configuration values containing trailing carriage returns, creating a path for unintended script execution during submodule initialization. According to Armis, the flaw can be abused when an attacker can influence the relevant configuration context, potentially turning routine clone or submodule operations into code execution. Microsoft’s Security Update Guide also lists the issue, identifying it as a Git/GitHub vulnerability. Public exploit activity quickly followed disclosure, with multiple GitHub repositories publishing proof-of-concept material for **CVE-2025-48384**, including variants described as working over HTTPS and others explicitly labeling the issue as carriage-return-driven remote code execution on cloning. The appearance of several PoC repositories indicates that exploit details are broadly accessible, increasing the likelihood of weaponization against developers and build environments that process untrusted repositories or submodules.
Jun 29, 2026
Researchers disclosed a Windows arbitrary code execution flaw in the Cursor AI coding IDE that causes the application to automatically run a malicious `git.exe` placed in the root of a repository when the project is opened. Mindgard said the issue stems from Cursor's Git path resolution logic searching the workspace itself for Git binaries, enabling attacker-controlled code to execute with the developer's privileges without clicks, prompts, or warnings; the payload may also be triggered repeatedly during normal use. In a demonstration, Mindgard renamed Windows Calculator to `git.exe` and showed Cursor launched it simply by opening the poisoned repository. Mindgard said it first reported the vulnerability to Cursor in December 2025, later resubmitted it through HackerOne after contacting the company's CISO, and that the flaw was still present in Cursor version `3.2.16` as of late April 2026 and in the latest version it tested before publication. Cursor told Dark Reading it was addressing the issue. Until a fix is available, Mindgard urged developers to open untrusted repositories only in isolated environments and recommended enterprise Windows controls such as **AppLocker** or **Windows App Control** to reduce exploitation risk.
Jul 18, 2026
Warp disclosed and patched multiple command injection vulnerabilities that could let attacker-controlled input reach shell commands in the terminal and development environment. One flaw, tracked as **CVE-2026-48732** / `GHSA-qqpc-wvvw-4269`, affected legacy SSH background command handling from version `v0.2023.03.21.08.02.stable_00` onward. Malicious remote host, repository, or directory names could inject shell syntax into helper commands used for SSH-backed metadata collection, allowing command execution on the remote host with the victim’s authenticated SSH account after user interaction in an affected legacy SSH session. Warp said the issue was fixed by escaping embedded single quotes in the remote working directory and released patched versions including `v0.2026.05.06.15.42.stable_01` and `v0.2026.05.13.09.15.stable_01`. A separate high-severity flaw, **CVE-2026-48719**, affected Warp versions from `0.2025.08.06.08.12.stable_00` through `0.2026.05.06.15.42.stable_01` and allowed a malicious Git branch name to be interpreted by the victim’s shell when selected from Warp’s prompt branch selector. Warp’s June code changes also show broader hardening of remote SSH session handling, including shell-specific escaping for single quotes before constructing commands such as `cd` and `cat`, plus tests covering Bash, Zsh, Fish, and PowerShell to keep crafted paths inert. The combined disclosures indicate that untrusted repository metadata and remote session context could be weaponized for command execution unless users upgrade to fixed releases.
Jun 29, 2026