ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-114098

Dulwich: Symlink directory traversal in stash pop allows arbitrary file write via intermediate directory symlinks

Published Oct 2, 2026 · catalog updated Oct 21, 2026 · Dulwich: Symlink directory traversal

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-114098. A missing EPSS score is not a low risk. Compare Dulwich: Symlink directory traversal with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Dulwich: Symlink directory traversal).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High8.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
PyPI dulwich

## Summary Dulwich's function is vulnerable to symlink directory traversal, allowing an attacker to write arbitrary files outside the repository worktree when a victim pops a stash in a malicious repository. ## Root Cause The function at uses to check if a parent directory exists before writing stashed files. follows symlinks, so when an intermediate directory in the path is a symlink pointing outside the worktree (e.g., ), the check passes and subsequent file writes resolve through the symlink. The function (line 228) only validates path component names against — it performs zero filesystem symlink detection. On dulwich 1.2.7 (latest release), has no symlink protection whatsoever. ## Impact An attacker can craft a malicious repository that, when a victim clones it and performs a stash pop operation, writes attacker-controlled content to arbitrary filesystem locations. Writing to achieves Remote Code Execution on the victim's machine on the next git checkout operation. ## Attack Scenario 1. Attacker creates a repository with branch containing (symlink → ) and branch containing (executable payload) 2. Victim clones the repository (landing on — symlink exists in worktree) 3. Victim checks out , makes changes, runs 4. Victim checks out (restoring the symlink) 5. Victim runs — stash contains 6. returns True (symlink to existing directory), skipped 7. → follows the intermediate symlink → payload written to 8. Next checkout operation triggers the hook → RCE ## Suggested Fix Before writing any file, verify that no component of the target path resolves through a symlink outside the worktree. Use and confirm it stays within the repository root. Alternatively, use with on each path component. Reported by **zx (Jace)**

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI dulwich0.22.5 → 1.2.8

How to fix CVE-2026-114098

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-114098. A missing EPSS score is not a low risk. Compare Dulwich: Symlink directory traversal with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0.22.5 → 1.2.8. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-22: Path Traversal; CWE-59: Link Following. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 2, 2026 · GitHub Advisory Database

    Detected

    ## Summary Dulwich's function is vulnerable to symlink directory traversal, allowing an attacker to write arbitrary files outside the repository worktree when a victim pops a stash in a malicious repository. ## Root Cause The function at uses to check if a parent directory exists before writing stashed files. follows symlinks, so when an intermediate directory in the path is a symlink pointing out

  2. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    dulwich fixed in 1.2.8

  3. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    dulwich fixed in 1.2.8

  4. Oct 21, 2026 · GitHub Advisory Database

    Updated

    ## Summary Dulwich's function is vulnerable to symlink directory traversal, allowing an attacker to write arbitrary files outside the repository worktree when a victim pops a stash in a malicious repository. ## Root Cause The function at uses to check if a parent directory exists before writing stashed files. follows symlinks, so when an intermediate directory in the path is a symlink pointing out

Sources

  • CVE.orgVulnerability recordCVE-2026-114098

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-cm62-gvxx-vmxx

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-cm62-gvxx-vmxx

    Dulwich: Symlink directory traversal in stash pop allows arbitrary file write via intermediate directory symlinks

    osv.dev
  • PyPA Advisory DatabasePackage advisoryGHSA-cm62-gvxx-vmxx

    Dulwich: Symlink directory traversal in stash pop allows arbitrary file write via intermediate directory symlinks

    osv.dev

References

Freshness

Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.