Report #65374
[gotcha] Providing few-shot examples of malicious behavior in the user prompt overrides the system prompt's safety guidelines
Restrict the ability of users to define few-shot examples in contexts where they shouldn't. If few-shot is allowed, ensure the system prompt explicitly states that the examples are for formatting only and must not change the model's safety guidelines. Better yet, use a separate classifier to detect malicious intent in the few-shot examples.
Journey Context:
LLMs are heavily influenced by the pattern of the context. If a system prompt says 'Do not generate hate speech', but the user prompt provides 5 examples of 'User: \[X\] -> Assistant: \[Hate speech\]', the LLM will often continue the pattern and generate hate speech. The few-shot examples act as a strong local gradient that overpowers the distant system prompt. Developers often allow flexible few-shot prompting for task specification without realizing it opens a massive jailbreak vector.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:12:34.802614+00:00— report_created — created