T5-AT-015HIGH
API Authentication Bypass
T5 · Model & API Exploitation →Risk score230
RatingHigh
Procedures10
Severity
Mechanism
LLM API authentication typically relies on bearer tokens (API keys), OAuth flows, or JWT-based session tokens. The design assumption is that the authentication layer is distinct from and independent of the model layer. The gap: LLM API authentication systems inherit all traditional web API authentication vulnerabilities, but with higher impact because LLM APIs provide direct access to expensive compute resources and potentially sensitive data.
Detection
- Monitor for authentication probing patterns (systematic key format testing)
- Scan for publicly exposed LLM API endpoints (continuous external scanning)
- Alert on API key usage from unexpected IP ranges or geographies
- Track per-key endpoint access patterns — alert on out-of-scope endpoint use
Mitigation
Authentication on ALL endpoints (including Ollama, vLLM defaults)HIGH
Network segmentation (LLM APIs never internet-facing)HIGH
Short-lived, scoped API keys with per-endpoint permissionsHIGH
API key rotation on regular scheduleMEDIUM
Chaining
Authentication bypass provides the initial access that enables every other T5 technique. Zero-auth discovery (T5-AP-015G) is the most common entry point in the wild, enabling immediate exploitation of T5-AT-001 through T5-AT-016.
Framework mapping
Open in the technique browser →OWASP LLMLLM02
MITRE ATLASAML.T0040