CVE-2026-29870
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA directory traversal vulnerability in the agentic-context-engine (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 does not normalize or validate filesystem paths, permitting traversal sequences (e.g., ../../../') to escape the intended checkpoint directory and overwrite arbitrary files accessible to the application process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed version of agentic-context-engineRun 'pip show agentic-context-engine' or 'pip list | grep agentic-context-engine' to identify the installed versionAffected if The installed version is 0.7.1 or lower (including any pre-release versions up to 0.7.1)
-
Locate the ace/skillbook.py file in the installationRun 'python -c "import ace.skillbook; print(ace.skillbook.__file__)"' to find the file path, then inspect the save_to_file method for path validationAffected if The save_to_file method lacks os.path.realpath() canonicalization and directory boundary validation before file writes
-
Identify usage of OfflineACE.run with checkpoint_dirSearch codebase for 'OfflineACE' and 'checkpoint_dir' usage patterns: grep -r 'OfflineACE' and grep -r 'checkpoint_dir' in project Python filesAffected if OfflineACE.run is called with a checkpoint_dir parameter that could accept traversal sequences
-
Audit for files written outside intended checkpoint directoryReview application logs, filesystem, or compare known checkpoint directory contents against unexpected files in parent directories or sensitive system pathsAffected if Files exist in locations outside the intended checkpoint_dir that were created by the application process
You are affected if agentic-context-engine version 0.7.1 or lower is installed AND your code uses OfflineACE.run with the checkpoint_dir parameter without additional path validation layers in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict path validation and normalization in the save_to_file method to ensure all file writes remain within the designated checkpoint directory. Use os.path.realpath() to resolve absolute paths and verify the resolved path starts with the intended checkpoint directory prefix before allowing file operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29870 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data