Report #67694
[agent\_craft] Distinguishing theoretical vulnerability explanation from actionable exploitation
Allow explanations of vulnerabilities and generic Proof of Concepts \(PoCs\). Refuse to generate exploits tailored to a specific, real-world target \(IP, domain, specific software version in production\) unless it is clearly an authorized bug bounty context.
Journey Context:
Security researchers need PoCs to validate findings. Providing a generic exploit for a CVE is standard educational/defensive work. Providing a script aimed at \`example.com\` is offensive. The boundary is 'actionable material against a specific target,' which crosses from defense to attack.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:06:19.941145+00:00— report_created — created