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

Advisory record · `GHSA-cm62-gvxx-vmxx`

- **Identifiers:** `GHSA-cm62-gvxx-vmxx` · `CVE-2026-114098`
- **State:** Confirmed
- **Severity:** CVSS 7.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-59](https://cwe.mitre.org/data/definitions/59.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 2 Oct 2026
- **Updated:** 21 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Oct 2026, 18:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `dulwich` (PyPI): affected `>=0.22.5, <1.2.8`; fixed in `1.2.8`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Dulwich versions 0.22.5 up to (but not including) 1.2.8 are vulnerable to a symlink directory traversal in the stash pop operation, which can write files outside the repository worktree. An attacker who supplies a malicious repository can get a victim to clone it and pop a stash, causing attacker-controlled content to be written to arbitrary locations, such as git hooks that run code on a later checkout. Upgrade dulwich to version 1.2.8 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.3 High, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-cm62-gvxx-vmxx)

## Sources

- [GitHub Advisory Database: GHSA-cm62-gvxx-vmxx](https://github.com/advisories/GHSA-cm62-gvxx-vmxx)
- [OSV: GHSA-cm62-gvxx-vmxx](https://osv.dev/vulnerability/GHSA-cm62-gvxx-vmxx)
- <https://github.com/jelmer/dulwich/security/advisories/GHSA-cm62-gvxx-vmxx>
- <https://github.com/jelmer/dulwich/commit/40a542cb02f9ac39a9eeac1193472903098698f9>
- <https://github.com/jelmer/dulwich>
- <https://github.com/jelmer/dulwich/releases/tag/dulwich-1.2.8>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cm62-gvxx-vmxx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cm62-gvxx-vmxx/>. Everything for agents: <https://agentprime.io/llms.txt>.