Is zeptoclaw safe to use? Its security history

Every advisory, newest first

• VulnerabilityGHSA-4cm8-xpfv-jv6f · 2026-03-12ZeptoClaw: Email Sender Spoofing to bypass Header-Only From Allowlist Validation
• VulnerabilityGHSA-2m67-cxxq-c3h8 · 2026-03-12ZeptoClaw: Path boundary checks bypass via symlink, TOCTOU, and hardlink
• VulnerabilityGHSA-46q5-g3j9-wx5c · 2026-03-12ZeptoClaw: Generic webhook channel trusts caller-supplied identity fields; allowlist is checked against untrusted payload data
• VulnerabilityGHSA-5wp8-q9mx-8jx8 · 2026-03-05zeptoclaw has Shell allowlist-blocklist bypass via command/argument injection and file name wildcards
• VulnerabilityGHSA-hhjv-jq77-cmvx · 2026-03-05zeptoclaw has Android device shell blocklist bypass via argument permutation

Check your version

Run cargo tree -i zeptoclaw to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.

RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.