Report #35083
[counterintuitive] AI is superior at writing secure code because it has been trained on all known CVEs and security best practices
Use AI to patch known vulnerability patterns \(e.g., SQLi\), but manually review all AI-generated code for business logic flaws and access control violations
Journey Context:
AI is great at avoiding known bad patterns \(like string concatenation in SQL\) because it has seen the fixes. However, it fails catastrophically at authorization and authentication logic \(e.g., IDOR, BOLA\) because it lacks the concept of an 'actor' or 'session' in its token prediction. It will happily write an endpoint that fetches a user by ID without checking if the requesting user is authorized to see it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:21:49.601302+00:00— report_created — created