# Dulwich symlink directory traversal in filter-branch index_filter

Source: https://junglewise.ai/threats/dulwich-symlink-directory-traversal-in-filter-branch-index-filter-via-c34daf58  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-02. Updated: 2026-10-02  
License: CC BY 4.0 with a link back

Severity: high · CVSS 8.6 · Published 2026-10-02

Dulwich is a Python library for interacting with Git repositories. When running filter-branch with an index filter on a malicious repository, symlinks from earlier commits can persist in the working directory and redirect subsequent writes to arbitrary filesystem locations. An attacker can exploit this to write files to sensitive locations like Git hooks, potentially achieving remote code execution.

Technologies: [Dulwich](https://junglewise.ai/threats/technologies/dulwich-dulwich), [dulwich (PyPI)](https://junglewise.ai/threats/technologies/dulwich). Vendors: [Dulwich](https://junglewise.ai/threats/vendors/dulwich), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** High severity, with a CVSS score of 8.6, published 2 October 2026.

**Which products and versions are affected?** Dulwich 1.2.7 and earlier; dulwich (PyPI) >= 0.23.1, <= 1.2.7.

**Is there a fix for This vulnerability?** No fixed version is recorded yet. Clean the working directory between commit iterations in _apply_index_filter(), or validate that no intermediate path components are symlinks before writing files. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is This vulnerability attacked?** It is attacked over the network, in a software library.

**Am I affected?** Check whether you run Dulwich or dulwich (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix


Clean the working directory between commit iterations in _apply_index_filter(), or validate that no intermediate path components are symlinks before writing files.

## Technical details

The vulnerability exists in CommitFilter._apply_index_filter() which materializes tree entries (including symlinks) to the working directory via build_index_from_tree() but only cleans up the temporary index file, not the written files. When processing commits recursively, ancestor symlinks persist and are followed when writing descendant files, enabling arbitrary writes. build_file_from_blob() lacks symlink protection and validate_path_element only validates name patterns, not filesystem state.

## Affected products

- Dulwich Dulwich 1.2.7 and earlier

## Timeline

- 2026-10-02: disclosed

## Related threats

- [Dulwich arbitrary file write on Windows via unvalidated drive letters](https://junglewise.ai/threats/dulwich-arbitrary-file-write-rce-on-windows-via-unvalidated-drive-fc90311d)
- [Dulwich infinite loop denial of service in packfile object resolution](https://junglewise.ai/threats/dulwich-infinite-loop-denial-of-service-dos-in-packfile-object-d71acec7)
- [Dulwich symlink write-through in checkout via os.open](https://junglewise.ai/threats/dulwich-symlink-write-through-in-checkout-paths-via-raw-os-open-7e9ebad6)
- [Dulwich symlink directory traversal in stash pop](https://junglewise.ai/threats/dulwich-symlink-directory-traversal-in-stash-pop-allows-arbitrary-file-12378d39)
- [Jelmer Dulwich arbitrary code execution via submodule path traversal](https://junglewise.ai/threats/cve-2026-52726-jelmer-dulwich-arbitrary-code-execution-via-submodule-path)