PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-114096 jelmer CVE debrief

Dulwich's `porcelain.checkout(paths=[...])` writes files using raw `os.open(file_path, O_WRONLY|O_CREAT|O_TRUNC, mode)` followed by `f.write(obj.data)`, bypassing symlink protections and allowing arbitrary file writes. This occurs because the `_checked_worktree_path()` function only performs name validation and does not detect filesystem symlinks, leading to potential security risks in systems using Dulwich, particularly those using versions prior to 1.2.8. Defenders should assess exposure and prioritize updates.

Vendor
jelmer
Product
dulwich
CVSS
HIGH 7.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-02
Original CVE updated
2026-10-21
Advisory published
2026-10-02
Advisory updated
2026-10-21

Who should care

Defenders responsible for systems using Dulwich, particularly those using versions prior to 1.2.8, should assess exposure and prioritize updates. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-114096 allows arbitrary file writes via symlink bypass in Dulwich's checkout function, impacting system integrity and requiring immediate attention from defenders.

  • Arbitrary file writes via symlink bypass
  • Potential for data tampering or unauthorized access
  • Need for verification and updates to Dulwich
  • Potential impact on system integrity

Technical summary

The Dulwich library's `porcelain.checkout(paths=[...])` function writes files using raw `os.open` without symlink protections, allowing arbitrary file writes. This happens because `_checked_worktree_path()` only performs name validation and does not detect filesystem symlinks. Affected versions are prior to 1.2.8. Defenders should prioritize verifying and updating Dulwich versions to 1.2.8 or later and assess exposure in their environments. The CVE record and source item provide details on the vulnerability, including the affected versions and a patch in version 1.2.8.

Defensive priority

Defenders should prioritize verifying and updating Dulwich versions to 1.2.8 or later, and assess exposure in their environments.

Recommended defensive actions

  • Verify and update Dulwich to version 1.2.8 or later
  • Assess exposure in environments using affected Dulwich versions
  • Implement additional monitoring for potential exploitation attempts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • 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
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including the affected versions and a patch in version 1.2.8. Evidence is limited to public CVE and source item data. Defenders should verify and update Dulwich to version 1.2.8 or later, assess exposure in their environments, and implement additional monitoring for potential exploitation attempts.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-114096 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-114096

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-114096 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-114096

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

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.