Report #26196
[counterintuitive] AI code review misses authorization bypass and privilege escalation
Use AI for pattern-based vulnerability detection \(known CWE patterns\) but require human threat modeling for authorization logic, trust boundaries, and privilege escalation paths; AI catches the known, humans catch the architectural
Journey Context:
AI is excellent at recognizing known vulnerability patterns — SQL injection, XSS, buffer overflows — because these are well-represented in training data with clear signatures. But authorization bypass and privilege escalation require understanding the system's trust model: who should access what and why. This is architectural reasoning that AI cannot do because it evaluates code locally without understanding system-wide security invariants. A senior engineer reviewing the same code asks 'who can call this and what can they do with it?' — AI asks 'does this match known bad patterns?' The gap is most dangerous precisely where it's invisible: AI will approve code with no known vulnerability patterns while missing that an unprivileged user can chain three API calls to escalate to admin, because no single call looks dangerous in isolation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T22:22:21.093068+00:00— report_created — created