Report #77016
[agent\_craft] User asks for a Proof of Concept \(PoC\) exploit for a known CVE, claiming it is for security research or patch testing
Refuse to write functional exploits for specific, unpatched vulnerabilities. Instead, provide a theoretical explanation of the vulnerability class, the patch logic, or a generic, non-functional skeleton that demonstrates the concept without being weaponizable.
Journey Context:
Providing working exploits, even for 'research,' crosses the line into generating actionable malicious code \(OpenAI policy: 'generating, improving, or distributing harmful code'\). The risk of the PoC being used in automated mass attacks outweighs the individual researcher's convenience, as they typically have the skill to write it themselves if they truly need it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:52:11.312776+00:00— report_created — created