ZeptoClaw: Path boundary checks bypass via symlink, TOCTOU, and hardlink

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2026-32232: 0.64% estimated exploitation activity in the next 30 days; percentile 50.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Workspace boundary enforcement currently has three related bypass risks. This issue tracks fixing all three in one pull request. Details R1 - Dangling Symlink Component Bypass - What happens: Path validation can miss dangling symlink components during traversal checks. - Why it matters: A symlink that is unresolved at validation time can later resolve to an external location. - Impact: Read and write operations may escape workspace boundaries. - Affected area: src/security/path.rs (checksymlinkescape). R2 - TOCTOU Between Validation and Use - What happens: The path is validated first, then used later for filesystem operations. - Why it matters: A concurrent filesystem change can swap path components after validation but before open/write. - Impact: Race-based workspace escape is possible. - Affected area: Filesystem and file-consuming tools that call validatepathinworkspace before I/O. R3 - Hardlink Alias Bypass - What happens: A file inside workspace can be a hardlink to an…

Published by the source

12 Mar 2026, 16:37 UTC

Last modified by the source

13 Mar 2026, 13:36 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2m67-cxxq-c3h8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32232

Advisory: ZeptoClaw: Path boundary checks bypass via symlink, TOCTOU, and hardlink
IDs: CVE-2026-32232, GHSA-2m67-cxxq-c3h8
Record: https://patchnext.com/advisories/cve-2026-32232 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zeptoclaw 0.7.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io zeptoclaw: affected <= 0.7.5; fixed in 0.7.6

## Suggested inspection (read-only)
- crates.io zeptoclaw: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zeptoclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2m67-cxxq-c3h8 (GitHub-reviewed advisory GHSA-2m67-cxxq-c3h8 lists affected ranges: crates.io zeptoclaw >=0 <=0.7.5)

Commands are suggestions: review each one before running it.