# CVE-2026-124029: Kopia through 0.23.1 Path Traversal in Snapshot Restore via Directory Entry Names


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-wxf6-4gvx-qq4q

## What is CVE-2026-124029?

CVE-2026-124029 is a medium-severity vulnerability in kopia, published on 6 Nov 2026. 

### Official description

Kopia through 0.23.1 contains a path traversal vulnerability in copyDirectoryContent that allows users with repository write access to escape the restore directory via crafted entry names. Attackers can create snapshots whose directory manifest entries are named '..', so victims restoring with default options write attacker-chosen content outside the restore directory.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-124029?


## How do I fix CVE-2026-124029?

No fix has been published for CVE-2026-124029 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124029 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124029 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124029 and fix it if it is affected.

What it is: CVE-2026-124029 is a medium-severity vulnerability in kopia, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124029 exists.

Affected product: kopia. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124029/ (Markdown: https://insights.sbomify.com/CVE-2026-124029/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124029
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124029
- OSV: https://osv.dev/vulnerability/CVE-2026-124029

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124029/
Summaries are generated and may contain mistakes; the official description above is the record.