Skip to main content
CVE-2026-122299VulnerabilityPublished Updated

SUSE · Security update for python-dulwich

Affects SUSESource GCVE Database

0
Compare
Authoritative record:CVE-2026-122299· High 8.6

Not known to be exploited · CVSS 8.6 High : upgrade SUSE dulwich to 1.2.20 soon.

Data as of 22 Nov 2026, 11:41 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.6
CNA (VulnCheck)CVSS 3.18.8
Patch
Available – fixed in 1.2.20
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade dulwich to 1.2.20.

Affected software

ProductAffectedFixed in
jelmerdulwichAffected
  • <1.2.20
Fixed in
  • 1.2.20
GitHubdulwichpkg:github/dulwichOther threatsAffected
  • <1.2.20
Fixed in
  • 1.2.20

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update has been released by the SUSE Product Security Team to fix this vulnerability. Users of python-dulwich should apply the update to ensure the parsing issue is resolved. No additional mitigation steps are indicated.

Description

A security update for python-dulwich addresses a commit object parsing vulnerability (CVE-2026-122299) where the parsing function incorrectly resolves duplicate tree headers by selecting the last occurrence instead of the first. This flaw could lead to incorrect commit object processing.

References

Community reviews

Loading reviews…