# CVE-2026-29870: Path traversal in n/a

> Attackers can overwrite arbitrary files via path traversal in the checkpoint directory, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2026
- **Updated:** 31 Mar 2026
- **Also known as:** GHSA-7gc4-v478-jrmv

## What is CVE-2026-29870?

CVE-2026-29870 is a high-severity path traversal vulnerability in n/a, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A directory traversal vulnerability in the agentic-context-engine project versions up to 0.7.1 allows arbitrary file writes via the checkpoint_dir parameter in OfflineACE.run. The save_to_file method in ace/skillbook.py fails to normalize or validate filesystem paths, allowing traversal sequences to escape the intended checkpoint directory. This vulnerability allows attackers to overwrite arbitrary files accessible to the application process, potentially leading to application corruption, privilege escalation, or code execution depending on the deployment context.

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

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


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

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

## Is CVE-2026-29870 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29870 is a high-severity path traversal vulnerability in n/a, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29870 exists.

Affected product: n/a. 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-29870/ (Markdown: https://insights.sbomify.com/CVE-2026-29870/index.md)
```

## Sources

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

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