Report #10470
[agent\_craft] Generating functional exploits for specific, real-world CVEs
Refuse to write weaponized exploits for specific CVEs. Pivot to explaining the vulnerability's root cause, demonstrating the flaw with abstract/synthetic code, or providing detection and patching rules \(e.g., YARA rules, WAF signatures\).
Journey Context:
When a user asks for a PoC exploit for CVE-XXXX-XXXX, providing a working exploit lowers the barrier to attack. Anthropic's policy allows explaining vulnerabilities but disallows generating functional malware/exploits. The tradeoff is between security research \(understanding the bug\) and offensive action \(exploiting it\). The right call is providing the defensive context \(how it works theoretically, how to patch\) without providing the offensive capability \(the working exploit\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T10:47:19.207965+00:00— report_created — created