Is CVE-2026-114097 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114097 being exploited in the wild.

How severe is CVE-2026-114097?

High severity, with a CVSS score of 7.8, published 21 October 2026.

Which products and versions are affected?

Jelmer Dulwich 0.23.1 to 1.2.7.

Is there a fix for CVE-2026-114097?

Yes: fixed in 1.2.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114097 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-114097?

Check whether you run Jelmer Dulwich 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.

CVE-2026-114097: Dulwich path traversal in filter_branch CommitFilter

CVE-2026-114097 · Severity: high · CVSS 7.8 · Published 2026-10-21

Dulwich is a Python library for Git version control operations. An attacker can craft a malicious Git repository that, when processed by Dulwich's filter_branch command, writes files to arbitrary locations on the system via symlink traversal, potentially enabling remote code execution if a hook file is overwritten.

Technologies: Jelmer Dulwich. Vendors: Jelmer.

Quick answers

Is CVE-2026-114097 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114097 being exploited in the wild.
How severe is CVE-2026-114097?: High severity, with a CVSS score of 7.8, published 21 October 2026.
Which products and versions are affected?: Jelmer Dulwich 0.23.1 to 1.2.7.
Is there a fix for CVE-2026-114097?: Yes: fixed in 1.2.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114097 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-114097?: Check whether you run Jelmer Dulwich 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

Fixed in: 1.2.8

Technical details

A path traversal vulnerability exists in CommitFilter._apply_index_filter() where materialized tree entries (including symlinks) persist in the working directory between commits. An attacker can create a repository with an ancestor commit containing a symlink and a descendant commit with a file path that traverses the symlink, causing writes to arbitrary filesystem locations. The vulnerability requires the user to run filter_branch with an index filter on a malicious repository.

Affected products

Jelmer Dulwich 0.23.1 to 1.2.7

Timeline

2026-07-06: disclosed
2026-10-20: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.