Quick answers
- Is CVE-2026-122299 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122299 being exploited in the wild.
- How severe is CVE-2026-122299?
- High severity, with a CVSS score of 8.8, published 4 November 2026.
- Which products and versions are affected?
- Jelmer Dulwich before 1.2.20; Python Poetry Development Group Poetry 2.5.1.
- Is there a fix for CVE-2026-122299?
- Yes: fixed in Dulwich 1.2.20. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-122299 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-122299?
- Check whether you run Jelmer Dulwich or Python Poetry Development Group Poetry 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: Dulwich 1.2.20
Technical details
The vulnerability exists in Dulwich's _parse_commit function, which resolves duplicate tree headers to the last occurrence rather than the first, unlike git's behavior. An attacker can craft a commit object with two tree headers, causing git and code reviewers to see one tree while Dulwich-based tools (like Poetry) resolve to a different attacker-controlled tree. The attack requires crafting a malicious commit object and is exploitable when Poetry uses Dulwich for git dependency resolution.
Affected products
- Jelmer Dulwich before 1.2.20
- Python Poetry Development Group Poetry 2.5.1
Timeline
- 2026-11-04: disclosed