PatchSiren cyber security CVE debrief
CVE-2026-38974 Dulwich CVE debrief
Dulwich through 1.1.0 was found to be missing SSH host key verification in contrib/paramiko_vendor.py. This issue was reported in the CVE record and the NVD entry is currently being reviewed. The vulnerability allows for potential man-in-the-middle attacks if an attacker can intercept and modify the communication between the client and server. Users of Dulwich through version 1.1.0 who utilize SSH connections should verify their configurations to ensure proper host key verification is in place. Affected product deployments should be identified and owners assigned for follow-up.
- Vendor
- Dulwich
- Product
- Dulwich
- CVSS
- MEDIUM 5.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-15
- Original CVE updated
- 2026-07-16
- Advisory published
- 2026-07-15
- Advisory updated
- 2026-07-16
Who should care
Users of Dulwich through version 1.1.0 who utilize SSH connections should verify their configurations to ensure proper host key verification is in place. This includes operators, platform administrators, vulnerability management teams, and security teams who need to assess the impact of this vulnerability on their systems and take necessary actions.
Technical summary
The Dulwich library, specifically through version 1.1.0, contains a vulnerability in the contrib/paramiko_vendor.py file where SSH host key verification is not performed. This oversight could potentially allow for man-in-the-middle attacks if an attacker can intercept and modify the communication between the client and server. The vulnerability is classified as medium severity with a CVSS score of 5.3. Users of Dulwich through version 1.1.0 who utilize SSH connections should verify their configurations to ensure proper host key verification is in place.
Defensive priority
Medium priority due to the potential for interception and modification of sensitive data. This vulnerability requires immediate attention to prevent potential man-in-the-middle attacks.
Recommended defensive actions
- Verify Dulwich configurations for proper SSH host key verification.
- Update Dulwich to a version that includes SSH host key verification if available.
- Implement compensating controls such as additional authentication mechanisms.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
Evidence is limited; verification of the vulnerability and affected versions is needed. The Dulwich library, specifically through version 1.1.0, contains a vulnerability in the contrib/paramiko_vendor.py file where SSH host key verification is not performed. This oversight could potentially allow for man-in-the-middle attacks if an attacker can intercept and modify the communication between the client and server. Users of Dulwich through version 1.1.0 who utilize SSH connections should verify their configurations to ensure proper host key verification is in place.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-38974 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-38974
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-38974 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-38974
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/jelmer/dulwich
-
Source reference
Unverified legacy reference
URL: https://github.com/jelmer/dulwich/pull/2123
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.