Live › vulnerability › CVE-2026-114097
Go to dashboardDulwich, a pure-Python Git library, has a path traversal in CommitFilter._apply_index_filter() where a symlink from an ancestor commit redirects a later commit's file writes outside the working directory. An attacker who crafts such a repository can get code executed by writing into .git/hooks.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only projects that use dulwich from 0.23.1 up to but not including 1.2.8 are exposed, and only when they run CommitFilter or filter_branch over repositories that may come from outside. Services that just read or write their own commits with dulwich are less exposed. Teams not using dulwich, or already on 1.2.8, can skip it.
No product ranges from the sources yet.
pip show dulwich (or check the lockfile) and see whether the installed version is at least 1.2.8 and below 0.23.1 is out of range.CommitFilter or filter_branch from dulwich on repositories you did not create.1.2.8 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Dulwich from 0.23.1 before 1.2.8 contains a path traversal vulnerability in CommitFilter._apply_index_filter() that allows attackers to write files outside the working directory via symlinks persisting between commits. Attackers can craft a repository where an ancestor commit's symlink redirects a descendant commit's file writes during filter_branch, enabling code execution by writing into .git/hooks.
This page as .md · .json · in your agent: get_signal("CVE-2026-114097")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.