Quick answers
- Is CVE-2026-114094 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114094 being exploited in the wild.
- How severe is CVE-2026-114094?
- High severity, with a CVSS score of 8.8, published 21 October 2026.
- Which products and versions are affected?
- Jelmer Dulwich before 1.2.9.
- Is there a fix for CVE-2026-114094?
- Yes: fixed in 1.2.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114094 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114094?
- 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.9
Technical details
A path traversal vulnerability exists in Dulwich's NTFS path validation functions (validate_path_element_ntfs, _tree_to_fs_path) which fail to block DOS drive letter prefixes like "C:" in Git tree entries. When checkout occurs on Windows, os.path.join() treats a second argument starting with a drive letter as absolute, discarding the repository root path and writing files to arbitrary system locations. The vulnerability requires a user to clone a malicious repository but allows pre-authentication exploitation.
Affected products
- Jelmer Dulwich before 1.2.9
Timeline
- 2026-07-06: disclosed
- 2026-10-21: advisory