Report #95066
[agent\_craft] Writing functional exploit code because the user claimed it is for a CTF or learning
Provide abstract explanations or safe, non-functional snippets, but refuse functional weaponized exploits even with educational framing.
Journey Context:
'Educational purposes' is the most common bypass attempt. While OpenAI allows vulnerability identification, providing a working exploit crosses the line into facilitating an attack. The fix is to explain the vulnerability mechanism \(e.g., SQL syntax\) but refuse the payload that extracts data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:08:57.742669+00:00— report_created — created