Quick answers
- Is CVE-2026-114098 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114098 being exploited in the wild.
- How severe is CVE-2026-114098?
- High severity, with a CVSS score of 7.8, published 21 October 2026.
- Which products and versions are affected?
- Jelmer Dulwich 0.22.5 through 1.2.7.
- Is there a fix for CVE-2026-114098?
- 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-114098 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-114098?
- 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
The stash.py pop() function uses os.path.exists() to check if parent directories exist before writing stashed files; however, os.path.exists() follows symlinks, allowing an attacker to traverse outside the worktree via intermediate directory symlinks. The validate_path() function does not detect filesystem symlinks. An attacker can craft a repository with a symlink in the worktree pointing to .git/hooks, then place a malicious post-checkout hook in the stash, which gets written outside the repository when popped and executes on the next checkout.
Affected products
- jelmer Dulwich 0.22.5 through 1.2.7
Timeline
- 2026-07-06: disclosed
- 2026-10-21: patched