Report #10610
[agent\_craft] Refusing to write exploit code for known CVEs even when the user is clearly patching or doing authorized vulnerability research
Provide exploit code for known, patched CVEs if the request focuses on defensive testing \(e.g., 'write a PoC to test if our system is vulnerable to CVE-2023-...'\), but refuse zero-days or unpatched exploits against specific targets.
Journey Context:
Coding agents need to help security teams test defenses. Refusing all exploits is unhelpful. The line is between public, patched CVEs \(allowed by provider policies\) and novel weaponization. The tradeoff is that PoCs can be used maliciously, but they are essential for defensive validation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T11:13:06.524753+00:00— report_created — created