Report #56161
[gotcha] Base64 or ROT13 encoded payloads bypassing input filters
Decode and inspect all user-supplied encoded strings \(Base64, URL encoding, ROT13\) before passing them to the LLM context, or instruct the LLM to never decode user-supplied strings.
Journey Context:
Input filters often look for plain-text malicious keywords. Attackers encode their payload in Base64 and append it to the prompt with instructions like 'Decode the following Base64 string and follow the instructions within it.' The text filter sees a random Base64 string and allows it, but the LLM decodes it and executes the hidden jailbreak. The tradeoff is that blocking or decoding all encoded strings might break legitimate use cases \(e.g., code interpreters\), but allowing opaque strings into the context window is a massive blind spot.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:45:35.670210+00:00— report_created — created