https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 18:48:16 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-275914 EUVD-2026-275914 https://cve.radiocsirt.org/vuln/euvd-2026-275914 https://cve.radiocsirt.org/vuln/fkie_cve-2026-32232 <p>ZeptoClaw is a personal AI assistant. Prior to 0.7.6, there is a Dangling Symlink Component Bypass, TOCTOU Between Validation and Use, and Hardlink Alias Bypass. This vulnerability is fixed in 0.7.6.</p> <p>ZeptoClaw is a personal AI assistant. Prior to 0.7.6, there is a Dangling Symlink Component Bypass, TOCTOU Between Validation and Use, and Hardlink Alias Bypass. This vulnerability is fixed in 0.7.6.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-32232 https://cve.radiocsirt.org/vuln/ghsa-2m67-cxxq-c3h8 <p><strong>Affected:</strong> crates.io: zeptoclaw</p> <p>### Summary Workspace boundary enforcement currently has three related bypass risks. This issue tracks fixing all three in one pull request.</p> <p>### Details</p> <p>#### 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 (check_symlink_escape).</p> <p>#### 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 validate_path_in_workspace before I/O.</p> <p>#### R3 - Hardlink Alias Bypass - What happens: A file inside workspace can be a hardlink to an inode outside the intended workspace trust boundary. - Why it matters: Prefix and symlink checks can pass while data access still mutates or reads external content. - Impact: Policy bypass for read/write operations. - Affected area: Any tool that reads or writes via validated paths.</p> <p>#### Risk Matrix</p> <p>| ID | Risk | Severity | Likelihood | Impact | |---|---|---|---|---| | R1 | Dangling symlink component bypass | High | Medium | Workspace boundary escape for read/wri…</p> <p><strong>Affected:</strong> crates.io: zeptoclaw</p> <p>### Summary Workspace boundary enforcement currently has three related bypass risks. This issue tracks fixing all three in one pull request.</p> <p>### Details</p> <p>#### 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 (check_symlink_escape).</p> <p>#### 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 validate_path_in_workspace before I/O.</p> <p>#### R3 - Hardlink Alias Bypass - What happens: A file inside workspace can be a hardlink to an inode outside the intended workspace trust boundary. - Why it matters: Prefix and symlink checks can pass while data access still mutates or reads external content. - Impact: Policy bypass for read/write operations. - Affected area: Any tool that reads or writes via validated paths.</p> <p>#### Risk Matrix</p> <p>| ID | Risk | Severity | Likelihood | Impact | |---|---|---|---|---| | R1 | Dangling symlink component bypass | High | Medium | Workspace boundary escape for read/wri…</p> https://cve.radiocsirt.org/vuln/ghsa-2m67-cxxq-c3h8