docs: expand vulnerability reporting guidelines in SECURITY.md

This commit is contained in:
Jamieson O'Reilly
2026-02-10 15:16:42 +11:00
parent b39669d1b4
commit 0657d7c772

View File

@@ -4,9 +4,31 @@ If you believe you've found a security issue in OpenClaw, please report it priva
## Reporting
For full reporting instructions - including which repo to report to and how - see our [Trust page](https://trust.openclaw.ai).
Report vulnerabilities directly to the repository where the issue lives:
Include: reproduction steps, impact assessment, and (if possible) a minimal PoC.
- **Core CLI and gateway** — [openclaw/openclaw](https://github.com/openclaw/openclaw)
- **macOS desktop app** — [openclaw/openclaw](https://github.com/openclaw/openclaw) (apps/macos)
- **iOS app** — [openclaw/openclaw](https://github.com/openclaw/openclaw) (apps/ios)
- **Android app** — [openclaw/openclaw](https://github.com/openclaw/openclaw) (apps/android)
- **ClawHub** — [openclaw/clawhub](https://github.com/openclaw/clawhub)
- **Trust and threat model** — [openclaw/trust](https://github.com/openclaw/trust)
For issues that don't fit a specific repo, or if you're unsure, email **security@openclaw.ai** and we'll route it.
For full reporting instructions see our [Trust page](https://trust.openclaw.ai).
### Required in Reports
1. **Title**
2. **Severity Assessment**
3. **Impact**
4. **Affected Component**
5. **Technical Reproduction**
6. **Demonstrated Impact**
7. **Environment**
8. **Remediation Advice**
Reports without reproduction steps, demonstrated impact, and remediation advice will be deprioritized. Given the volume of AI-generated scanner findings, we must ensure we're receiving vetted reports from researchers who understand the issues.
## Security & Trust