Report #96633
[gotcha] Attackers force LLMs to process massive inputs, exhausting token limits and degrading safety
Enforce strict input length limits \(character and token counts\) before passing data to the LLM. Truncate RAG results and user inputs aggressively.
Journey Context:
Developers assume the LLM's context window is just a limit, not an attack surface. Attackers provide extremely long inputs \(e.g., a 100k character document\) or instruct the LLM to repeat a word forever. This can exhaust the context window, pushing the system prompt \(and safety instructions\) out of the active attention window, or cause massive API cost overruns. The LLM 'forgets' its safety rules because they are too far back in the context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:46:53.328415+00:00— report_created — created