LLM Jailbreak Taxonomy 2026: How the Techniques Cluster

The jailbreak ↗ literature is large, scattered, and inconsistently named. The same technique gets rediscovered every six months by a new paper with a new name. Defenders trying to evaluate coverage gaps are comparing lists of technique names that describe overlapping categories differently.

This taxonomy is an attempt to organize working LLM jailbreak techniques by the underlying behavioral property they exploit. The goal is a classification that’s useful for defenders assessing coverage, researchers identifying novel attack surfaces, and practitioners deciding which detection methods apply to which techniques. To filter the underlying technique classes by property, modality, and family, browse the interactive jailbreak index, which records each technique’s behavioral category and last-known status without publishing any working payload.

Behavioral properties: what jailbreaks exploit

Jailbreaks work because large language models have predictable failure modes. Every effective technique exploits one or more of the following properties:

1. Instruction-following overgeneralization The model is trained to follow instructions. Jailbreaks in this category reframe the request as an instruction the model should follow, overriding prior instructions through structural manipulation.

Examples: “Ignore previous instructions,” roleplay framing (“pretend you are an AI without restrictions”), hypothetical framing (“in a story where the AI could say anything…”), fictional nesting (instructions embedded in quoted dialogue).

2. Context window primacy Models attend more strongly to recent context. Techniques in this category exploit context position by placing the jailbreak close to the end of the context window, after system prompt content has been diluted.

Examples: Long prefix injection (flooding the context with benign text before the harmful request), context stuffing (filling the context with related but benign material that shifts the model’s framing), many-shot jailbreaking.

3. Persona adoption Models trained on dialogue data have internalized personas. Asking the model to adopt a different persona can activate training-data representations of that persona’s behavior.

Examples: “DAN” (Do Anything Now) variants, historical character impersonation, fictional AI system impersonation, “jailbroken version of yourself” prompts.

4. Gradient-exploited token sequences Adversarially crafted input sequences that exploit gradient information from the model’s weights. These are technically distinct from social-engineering techniques — they’re mathematically optimized inputs rather than natural-language framings.

Examples: Universal adversarial suffixes (Zou et al. 2023), GCG (Greedy Coordinate Gradient) attack variants. These often transfer across models in the same family.

5. Encoding and obfuscation Content policies are typically applied to surface-level text. Encoded or obfuscated requests can bypass classifiers that operate on decoded text, or exploit the gap between what the classifier sees and what the model processes.

Examples: Base64 encoding of the harmful request, ROT13, Morse code, leetspeak substitution, character-by-character instruction (“spell out each letter of the word ‘synthesize’ and then continue”).

6. Training data exploitation Models have seen harmful content in pretraining. Techniques in this category attempt to elicit training data through completion-style prompts that prime the model to reproduce patterns from that data.

Examples: Completion attacks (“the synthesis procedure begins with…”), fictional scenario completion where the story arc leads to harmful output, continuation attacks on partial harmful content.

Which models are most vulnerable to which techniques

As of early 2026, the published literature supports some general observations (JailbreakDB does not pair exact model names with technique mappings, to avoid creating a lookup table for attackers):

• Persona-adoption techniques (Category 3) have, according to published evaluations, been significantly hardened in frontier models since 2023. They remain more effective on smaller fine-tuned models and open-source models without RLHF hardening.
• Gradient-exploited techniques (Category 4) remain a research focus. As reported in the literature, they are computationally expensive to generate but transfer better than social-engineering techniques.
• Encoding techniques (Category 5) are inconsistently addressed. Many production deployments have content filters that operate on decoded output, not intermediate representations. Coverage varies by provider.
• Long-context techniques (Category 2) have become more relevant as context windows have expanded. More context → more opportunity for injection.

The defender’s view

This taxonomy is most useful for defenders as a coverage checklist. For each technique category, the questions are:

1. Does your detection layer operate at the right level to catch this?
2. Have your defenses been tested against representative samples from this category?
3. How does your defense degrade under adversarial optimization pressure?

A defense that covers Categories 1 and 3 but not Categories 4 and 5 has coverage gaps that sophisticated attackers will find.

For a comparison of detection tooling coverage across technique categories, bestllmscanners.com ↗ benchmarks scanners against representative samples from each category.

What’s not in this taxonomy

Multi-turn jailbreaks (where the jailbreak is spread across multiple conversation turns) are a distinct pattern not fully captured by single-turn technique categories. Indirect prompt injection — where the injected instruction comes from retrieved content rather than the user input — is covered separately in the prompt injection literature and tracked at promptinjection.report ↗.

Membership inference attacks, model inversion, and data extraction from fine-tuned models are different attack classes (they target training data, not safety constraints) and belong to a separate taxonomy.

How this database is maintained

Entries in JailbreakDB are sourced from peer-reviewed research, disclosed vulnerability reports, and responsible disclosure submissions. Each entry records the model family the source reported it against, the behavioral category it belongs to, and the last known working status as documented by that source. JailbreakDB does not publish specific prompts; it publishes technique patterns and the properties they exploit.

Submissions via the editor contact. We do not pay for technique descriptions; we attribute researchers who want attribution.