CVE-2026-122299
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-122299 is a high-severity Misinterpretation of Input (CWE-115) vulnerability. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Space after Filename (T1036.006); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-117194
Vulnerability Data
Dulwich before 1.2.20 contains a commit object parsing vulnerability where the read path in _parse_commit resolves a duplicate tree header to the last occurrence instead of the first, diverging from core git's resolution behavior, while Poetry 2.5.1 ships this version…
more
and uses dulwich by default for git dependency installation. Attackers can craft a commit object with two tree headers so that reviewers and CI using git see a benign tree while Poetry's dulwich-based checkout resolves to a different attacker-controlled tree containing malicious build scripts such as setup.py, resulting in unreviewed code execution on the install or build host.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.3.4V4.2.1V7.1.3V7.6.1
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Input validation directly stops the system from accepting and acting on misinterpreted data values.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require correct input parsing/validation to avoid misinterpretation flaws.
Runtime data monitoring can surface consistency violations after they occur.
Integrity protections such as hashes or signatures can detect or prevent inconsistent state copies.
Resilience mechanisms often include state synchronization or replication protocols that enforce consistency.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect input misinterpretation flaws but does not itself implement the preventive controls.
Secure coding standards require strict input validation and canonical forms to eliminate misinterpretation vulnerabilities.
A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary input-handling weaknesses in delivered code the way those practices do, at the clause's declared ceiling of `partial`.