CVE-2026-32232 is a critical path validation flaw in ZeptoClaw, a personal AI assistant, scored 9.8. Workspace boundary checks could be bypassed through dangling symlinks, a race between validation and use, and hardlinks. Upgrade ZeptoClaw to 0.7.6 or later. Checks and steps follow below.
What's affected
ZeptoClaw 0.7.5 and earlier. The patched version is 0.7.6.
The advisory lists three related bypasses that the fix covers together: a dangling symlink component, a time of check to time of use race, and a hardlink alias that points outside the workspace.
How to check if you're exposed
ZeptoClaw is a Rust project, so check the release tag or the version recorded in Cargo.lock for the build you run. Anything at 0.7.5 or earlier needs the upgrade.
What to do now
- Upgrade ZeptoClaw to 0.7.6 or later.
- Run the assistant as a low privilege user whose own files are limited to the workspace.
- Keep sensitive files outside directories the assistant can write to.
- Treat untrusted content that can create symlinks or hardlinks in the workspace with care.
Why it matters
The record lists CWE-22, path traversal, and CWE-62, UNIX hard link following. Checking that a path starts inside the workspace is not enough, because the filesystem can resolve it elsewhere. A symlink that does not exist yet can later point outside. A path can change between the check and the open. A hardlink can make a file inside the workspace share an inode with one outside.
The advisory says reads and writes could escape the boundary. For an assistant that edits files on your behalf, that boundary is the safety line. Good fixes open files relative to a checked directory handle and refuse links, instead of checking a string first.
The record does not flag this CVE as listed in CISA's Known Exploited Vulnerabilities catalog, and no advisory I read says it is exploited in the wild. Treat it as a patch to schedule promptly, not a fire drill, unless your own logs say otherwise.
Quick check
What is a TOCTOU race?
The program checks a path, then uses it later. If something changes the path between the two steps, the check no longer applies.
Sources
Last reviewed: 19 October 2026.
