Report #71067
[agent\_craft] Agent refuses to write a Proof of Concept \(PoC\) or explain a known vulnerability \(CVE\) because it involves exploit code
Allow generation of PoC code for publicly documented vulnerabilities \(CVEs\) if the intent is defensive \(testing patch efficacy, understanding the flaw\). Refuse only if asked to develop novel exploits for unpatched, zero-day vulnerabilities or to target specific third-party systems.
Journey Context:
Security professionals use coding agents to write detection logic and test patches. Blanket refusals on exploit code block legitimate defensive work. The line is drawn at novelty and targeting: explaining how a public CVE works is educational/defensive; creating a new exploit for a live target is offensive. This aligns with provider policies allowing vulnerability research.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:51:35.379132+00:00— report_created — created