| Version | Supported |
|---|---|
Latest on main |
Yes |
Email security@droxey.com with:
- Description of the vulnerability
- Steps to reproduce
- Impact assessment (which layer of the security model is affected)
We aim to respond within 48 hours and patch critical issues within 7 days.
Do not open a public GitHub issue for security vulnerabilities.
Clincher uses 9 hardening layers to lock down the AI agent:
- Network isolation —
openclaw-netisinternal: true(no direct internet) - Egress control — Smokescreen whitelists only HTTPS to LLM provider domains
- Socket proxy — EXEC/CONTAINERS/IMAGES/INFO only; BUILD/SECRETS/SWARM denied
- Container hardening —
cap_drop: ["ALL"],no-new-privilegesat daemon + container level - Sandbox isolation —
capDrop=["ALL"],network=none, no workspace access - Tool denials — 13 dangerous tools blocked at agent and gateway levels
- Credential handling — File-based secret passing; never CLI args
- SSH hardening — Non-standard port, key-only auth, deploy user only
- Firewall — UFW + fail2ban, admin IP whitelist, Cloudflare-only ingress
See the full deployment guide for implementation details.