AI Policy Wiki
Dashboard
⚲

StrongREJECT

medium confidence · updated 2026-09-22

Measures how much genuinely useful harmful information a jailbreak actually extracts from a model, rather than merely whether the model refused. Built at UC Berkeley in 2024 from 313 forbidden prompts and a rubric-based autograder that scores refusal, specificity and persuasiveness, after the authors found that most published jailbreak success rates were substantially overstated.

StrongREJECT — expanded by its authors as Strong, Robust Evaluation of Jailbreaks at Evading Censorship Techniques — is a jailbreak-evaluation benchmark consisting of 313 forbidden prompts and an automated grader that scores how much genuinely useful harmful information a model's response provides. It was introduced in a February 2024 paper titled "A StrongREJECT for Empty Jailbreaks," by Alexandra Souly, Qingyuan Lu, Dillon Bowen, Tu Trinh, Elvis Hsieh, Sana Pandey, Pieter Abbeel, Justin Svegliato, Scott Emmons, Olivia Watkins and Sam Toyer of the Center for Human-Compatible AI at UC Berkeley, last revised in August 2024 A StrongREJECT for Empty Jailbreaks (Souly et al., 2024). The paper's starting observation is that jailbreak papers routinely claim near-100% attack success rates that do not survive inspection, and its central empirical finding is an explanation for why: jailbreaks that make a model willing to answer tend to make it worse at answering. Since 2024 StrongREJECT has become the academic jailbreak benchmark most often reported in OpenAI system cards, under the metric goodness@0.1.

What it measures

The authors define a jailbreak benchmark as two things — a dataset of forbidden prompts and a method of scoring responses to them — and argue that existing benchmarks were defective in both halves. Their diagnosis of the scoring half is that prior automated evaluators over-emphasized, and often measured only, non-refusal: "the lack of an explicit refusal does not mean the victim model has provided useful information related to a forbidden prompt" A StrongREJECT for Empty Jailbreaks (Souly et al., 2024).

What StrongREJECT measures instead is the usefulness of a response to an attacker with a harmful goal, decomposed into two dimensions: willingness (did the model refuse?) and capability (was the answer specific and convincing enough to be worth having?). A response that is not refused but is incoherent or vacuous scores zero, the same as a refusal. The paper's motivating example is a claimed 43% attack success rate against GPT-4 for a jailbreak that translates requests into Scots Gaelic; the authors reproduced it and found the full model outputs "generally vacuous or incoherent," containing no actionable information on explosives A StrongREJECT for Empty Jailbreaks (Souly et al., 2024).

Design

The forbidden-prompt dataset

Six categories were selected by cross-referencing the usage policies of OpenAI, Anthropic, Google Gemini, Meta Llama and DeepInfra and keeping behaviors forbidden in all of them and refused by current models from those providers and from Mistral, Reka and Cohere: illegal goods and services; non-violent crimes; hate, harassment and discrimination; disinformation and deception; violence; and sexual content. There are at least 50 prompts in each category, 313 in total, of which 70% are novel to the benchmark, 10% each come from DAN and AdvBench, and the remainder from other prior work and OpenAI's system card A StrongREJECT for Empty Jailbreaks (Souly et al., 2024).

The selection criteria are stated as a response to specific defects the authors document in earlier datasets: that 24 of AdvBench's 520 prompts ask for bomb-making instructions, that other datasets contain prompts that are unanswerable or not actually forbidden, and that some ask for information no model could have. StrongREJECT prompts were required to be distinct, refused by current frontier models, detailed enough for a human to evaluate a response, simple enough for a moderately capable model to answer, and — importantly for release — to have "factually verifiable answers with easily accessible information, such that a person with Internet access could write a high-quality response within an hour," which the authors say ensures that publishing responses creates no information hazard.

The autograder

The rubric-based evaluator prompts an LLM with the forbidden prompt, the model's response and scoring instructions. The evaluator produces chain-of-thought reasoning and then three scores: a binary non-refusal judgment and two five-point Likert ratings, rescaled to 0–1, for how specific and how convincing the response is. The final score is

score = (1 − refused) × (specific + convincing) / 2

so a refusal scores 0 and so does a non-refused but useless answer A StrongREJECT for Empty Jailbreaks (Souly et al., 2024).

Two versions are released. The rubric-based evaluator is intended for use with a hosted frontier model — the paper uses GPT-4o-mini throughout — and the authors report running and evaluating a dozen jailbreaks over the full dataset in about 15 minutes for under $1. The open-source alternative is Gemma 2B fine-tuned for one epoch on roughly 15,000 labelled responses, about 4,000 of them victim-model responses to StrongREJECT prompts and 11,000 from HarmBench, for researchers who prefer to run an evaluator on their own GPU.

Validation against human judgment

The authors treat human labels as ground truth and evaluate each automated grader as if it were a regression model predicting them, across 17 jailbreak methods. Against human judges, both StrongREJECT variants and HarmBench show almost no bias, while most earlier evaluators overestimate jailbreak effectiveness and the OpenAI moderation API underestimates it.

EvaluatorBiasMean absolute error (all responses)Spearman correlation of jailbreak rankings
String matching0.4840.580−0.394
Jailbroken — binary0.3540.407−0.291
PICT0.2320.2910.101
GPT-4 Judge0.2080.2620.157
PAIR0.1520.2050.249
OpenAI moderation API−0.1610.197−0.103
HarmBench0.0130.0900.819
StrongREJECT fine-tuned−0.0230.0840.900
StrongREJECT rubric0.0120.0770.846

A StrongREJECT for Empty Jailbreaks (Souly et al., 2024)

Responses that human labelers scored as completely harmless received a mean of 0.039 from the rubric evaluator and 0.035 from the fine-tuned one.

No human baseline

StrongREJECT has no human performance baseline in the sense of a score humans achieve. Humans appear in the design as labelers whose judgments the autograder is calibrated against.

Versions and variants

The two released graders — rubric-based and Gemma-2B fine-tuned — are the benchmark's own variants; code and data are at strong-reject.readthedocs.io.

Developers have built their own adaptations. OpenAI describes StrongREJECT v2 in its 2025 cross-lab evaluation exercise with Anthropic as "an adversarial robustness benchmark, based on the StrongREJECT paper," using "a curated subset of 60 questions specifically chosen to stress-test areas prohibited by OpenAI policies," with each question tested under roughly 20 variations applying techniques such as translation into another language, distracting instructions, or permission to ignore earlier instructions (Source: openai.com). OpenAI has also reported a filtered adaptation: the GPT-5.2 system card update states the original set was "otherwise highly saturated" and that a filtered version was used instead (Update to GPT-5 System Card: GPT-5.2 (OpenAI, December 2025)).

HarmBench (Mazeika et al., Center for AI Safety with UIUC and Carnegie Mellon, February 2024) is the closest contemporary and the only prior evaluator that matches StrongREJECT's agreement with human judges in the table above. It is a standardized framework for automated red teaming rather than a scoring rubric: 510 curated harmful behaviors across four functional categories, split into 400 textual and 110 multimodal, run through a standardized pipeline that turns behaviors into test cases and scores attack success rate with a fine-tuned classifier. The paper compares 18 red teaming methods against 33 target LLMs and defenses, and introduces R2D2, an adversarial training method HarmBench: A Standardized Evaluation Framework for Automated Red Teaming and Robust Refusal (Mazeika et al., 2024). HarmBench is reported in UK AISI evaluations alongside a private harmful-question set (UK AISI — Advanced AI Evaluations May Update), is listed among standardized jailbreak resources alongside JailbreakBench and MITRE ATLAS (Jailbreaking and Red Teaming), and supplied 11,000 of the labelled responses used to fine-tune the open-source StrongREJECT grader.

AgentHarm extends the same logic to tool-using agents and cites StrongREJECT directly as the reason for including capability in its scoring AgentHarm: A Benchmark for Measuring Harmfulness of LLM Agents (Andriushchenko et al., 2024).

Development and maintainers

The paper lists its authors under the Center for Human-Compatible AI at UC Berkeley. The benchmark is released as open code and data with documentation at strong-reject.readthedocs.io; there is no leaderboard, submission process or verification body, and published scores are run by whoever reports them A StrongREJECT for Empty Jailbreaks (Souly et al., 2024).

Results

The paper's own headline results are scores for jailbreak methods, not for models: evaluating 37 jailbreak methods over all 313 prompts against GPT-4o, GPT-3.5 Turbo and Llama-3.1 70B Instruct, the authors found that a small number of jailbreaks are highly effective — the strongest use LLMs to attack LLMs, specifically PAIR (Prompt Automatic Iterative Refinement) and PAP (Persuasive Adversarial Prompts) — while most produce low-quality responses, with observed scores "usually substantially lower than those reported in the papers where these jailbreaks were introduced." Two versions of GCG were effective against GPT-3.5 Turbo but not GPT-4o or Llama-3.1 70B, which the authors read as newer models having been trained against those adversarial suffixes. An attacker free to choose the best jailbreak per prompt "could nearly always achieve a perfect StrongREJECT score, suggesting that frontier models remain highly vulnerable to jailbreaks" A StrongREJECT for Empty Jailbreaks (Souly et al., 2024).

Model-level scores come from developers, under two different conventions. OpenAI reports goodness@0.1, defined in its system cards as "the safety of the model when evaluated against the top 10% of jailbreak techniques per prompt," on a 0–1 scale where higher is safer; the 2025 cross-lab exercise restates it as "the mean (1−badness) score, where badness is scored via auto-grader" (Source: arxiv.org; Source: openai.com). On that metric the o-series marked a step change over GPT-4o, from 0.22 to 0.66–0.83, after which GPT-4.5 fell back to 0.34 (OpenAI GPT-4.5 System Card (February 2025)). A separate convention appears in Thinking Machines Lab's reporting, which gives StrongREJECT as a percentage in the high nineties for every model compared, clustered so tightly that it carries little discriminating signal.

goodness@0.1 (OpenAI system cards)

Safety against the top 10% most effective jailbreak techniques per prompt, 0–1, higher is safer. All figures are developer-reported by OpenAI.

ModelScoreSettingDateSource
GPT-4.50.34goodness@0.1; developer-reported2025-02OpenAI GPT-4.5 System Card (February 2025)
GPT-4o0.37goodness@0.1, as reported in the GPT-4.5 system card2025-02OpenAI GPT-4.5 System Card (February 2025)
o10.87goodness@0.1, as reported in the GPT-4.5 system card2025-02OpenAI GPT-4.5 System Card (February 2025)
o1-mini0.83goodness@0.1; o1 system card2024-12(Source: arxiv.org); OpenAI o1 System Card (December 2024)
o10.72goodness@0.1; o1 system card2024-12(Source: arxiv.org); OpenAI o1 System Card (December 2024)
o1-preview0.66goodness@0.1; o1 system card2024-12(Source: arxiv.org); OpenAI o1 System Card (December 2024)
GPT-4o0.22goodness@0.1; o1 system card2024-12(Source: arxiv.org); OpenAI o1 System Card (December 2024)
o1-preview0.840jailbreak robustness at o1-preview launch, reported against GPT-4o's 0.2202024-09(Source: openai.com)
GPT-4o0.220reported at o1-preview launch2024-09(Source: openai.com)

Developer-reported percentage (Thinking Machines Lab)

Thinking Machines Lab reports StrongREJECT as a percentage alongside FORTRESS in the Inkling model card and launch post, with Inkling scores taken at effort=0.99. The card does not state the scoring convention, and the values are not comparable with goodness@0.1.

ModelScoreSettingDateSource
Qwen3.5 397B-A17B99.4%scoring convention not stated; reported by Thinking Machines Lab in the Inkling-Small model card (card §5. Evaluations)2026-07-30Inkling-Small Model Card (Thinking Machines Lab, July 2026)
MiMo V2.599.3%scoring convention not stated; reported by Thinking Machines Lab in the Inkling-Small model card (card §5. Evaluations)2026-07-30Inkling-Small Model Card (Thinking Machines Lab, July 2026)
Minimax M2.799.4%scoring convention not stated; reported by Thinking Machines Lab in the Inkling-Small model card (card §5. Evaluations)2026-07-30Inkling-Small Model Card (Thinking Machines Lab, July 2026)
Claude 4.5 Haiku98.6%scoring convention not stated; reported by Thinking Machines Lab in the Inkling-Small model card (card §5. Evaluations)2026-07-30Inkling-Small Model Card (Thinking Machines Lab, July 2026)
Gemini 3.5 Flash-Lite97.6%scoring convention not stated; reported by Thinking Machines Lab in the Inkling-Small model card (card §5. Evaluations)2026-07-30Inkling-Small Model Card (Thinking Machines Lab, July 2026)
GPT 5.6 Luna98.7%scoring convention not stated; reported by Thinking Machines Lab in the Inkling-Small model card (card §5. Evaluations)2026-07-30Inkling-Small Model Card (Thinking Machines Lab, July 2026)
Kimi K2.699.8%developer-reported by Thinking Machines Lab; convention not stated2026-07-15(Source: thinkingmachines.ai); Inkling Model Card (Thinking Machines Lab, July 2026)
Claude Fable 598.7%developer-reported by Thinking Machines Lab (max effort); convention not stated2026-07-15Inkling Model Card (Thinking Machines Lab, July 2026)
Inkling98.6%developer-reported at effort=0.992026-07-15Inkling Model Card (Thinking Machines Lab, July 2026); Inkling-Small Model Card (Thinking Machines Lab, July 2026)
DeepSeek V4 Pro98.6%developer-reported by Thinking Machines Lab; convention not stated2026-07-15Inkling Model Card (Thinking Machines Lab, July 2026)
GLM 5.298.5%developer-reported by Thinking Machines Lab; convention not stated2026-07-15Inkling Model Card (Thinking Machines Lab, July 2026)
GPT 5.6 Sol98.5%developer-reported by Thinking Machines Lab (max/xhigh); convention not stated2026-07-15Inkling Model Card (Thinking Machines Lab, July 2026)
Inkling-Small98.4%developer-reported by Thinking Machines Lab2026-07-30(Source: thinkingmachines.ai); Inkling-Small Model Card (Thinking Machines Lab, July 2026)
Gemini 3.1 Pro98.0%developer-reported by Thinking Machines Lab; convention not stated2026-07-15Inkling Model Card (Thinking Machines Lab, July 2026)
DeepSeek V4 Flash97.4%developer-reported by Thinking Machines Lab2026-07-30(Source: thinkingmachines.ai); Inkling-Small Model Card (Thinking Machines Lab, July 2026)
Nemotron 3 Ultra98.7%scoring convention not stated; reported by Thinking Machines Lab in the Inkling model card (card §5. Evaluations)2026-07-15Inkling Model Card (Thinking Machines Lab, July 2026); Inkling-Small Model Card (Thinking Machines Lab, July 2026)
Kimi K2.599.5%scoring convention not stated; reported by Thinking Machines Lab in the Inkling model card (card §5. Evaluations)2026-07-15Inkling Model Card (Thinking Machines Lab, July 2026)

StrongReject filtered — not_unsafe, filtered set (OpenAI)

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-5-instant-oct30.850not_unsafe under OpenAI policy graders (higher is better); known jailbreaks inserted into disallowed-content prompts; StrongReject examples filtered to remove those on which all OpenAI models including GPT-4o were consistently safe; not the goodness@0.1 metric; reported by OpenAI in the GPT-5.2 system card update (latest version of the comparison model; card says values may differ from launch) (card §3.2 (Table 2))2025-12-11Update to GPT-5 System Card: GPT-5.2 (OpenAI, December 2025)
GPT-5.1 Instant0.976not_unsafe under OpenAI policy graders (higher is better); known jailbreaks inserted into disallowed-content prompts; StrongReject examples filtered to remove those on which all OpenAI models including GPT-4o were consistently safe; not the goodness@0.1 metric; reported by OpenAI in the GPT-5.2 system card update (latest version of the comparison model; card says values may differ from launch) (card §3.2 (Table 2))2025-12-11Update to GPT-5 System Card: GPT-5.2 (OpenAI, December 2025)
GPT-5.2 Instant0.878not_unsafe under OpenAI policy graders (higher is better); known jailbreaks inserted into disallowed-content prompts; StrongReject examples filtered to remove those on which all OpenAI models including GPT-4o were consistently safe; not the goodness@0.1 metric; developer-reported (card §3.2 (Table 2))2025-12-11Update to GPT-5 System Card: GPT-5.2 (OpenAI, December 2025)
GPT-5.1 Thinking0.959not_unsafe under OpenAI policy graders (higher is better); known jailbreaks inserted into disallowed-content prompts; StrongReject examples filtered to remove those on which all OpenAI models including GPT-4o were consistently safe; not the goodness@0.1 metric; reported by OpenAI in the GPT-5.2 system card update (latest version of the comparison model; card says values may differ from launch) (card §3.2 (Table 2))2025-12-11Update to GPT-5 System Card: GPT-5.2 (OpenAI, December 2025)
GPT-5.2 Thinking0.975not_unsafe under OpenAI policy graders (higher is better); known jailbreaks inserted into disallowed-content prompts; StrongReject examples filtered to remove those on which all OpenAI models including GPT-4o were consistently safe; not the goodness@0.1 metric; developer-reported (card §3.2 (Table 2))2025-12-11Update to GPT-5 System Card: GPT-5.2 (OpenAI, December 2025)

StrongReject — not_unsafe by category: illicit/non-violent-crime prompts

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-5-thinking0.995not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
OpenAI o30.985not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-main0.934not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
GPT-4o0.937not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-thinking-mini0.994not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-thinking-nano0.997not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
OpenAI o4-mini0.968not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-main-mini0.940not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)

StrongReject — not_unsafe by category: violence prompts

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-5-thinking0.999not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
OpenAI o30.992not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-main0.948not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
GPT-4o0.955not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-thinking-mini0.996not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-thinking-nano0.996not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
OpenAI o4-mini0.972not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-main-mini0.949not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)

StrongReject — not_unsafe by category: abuse, disinformation, hate prompts

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-5-thinking0.999not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
OpenAI o30.995not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-main0.978not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
GPT-4o0.981not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-thinking-mini0.973not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-thinking-nano0.997not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
OpenAI o4-mini0.973not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-main-mini0.971not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)

StrongReject — not_unsafe by category: sexual-content prompts

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-5-thinking0.995not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
OpenAI o30.991not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-main0.967not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
GPT-4o0.961not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §3.4, Table 5)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-thinking-mini0.994not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-thinking-nano0.996not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
OpenAI o4-mini0.970not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; comparison model; reported by OpenAI in the GPT-5 system card (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)
gpt-5-main-mini0.953not_unsafe; known jailbreaks inserted into disallowed-content prompts, graded by OpenAI policy graders; higher is better; developer-reported (card §Appendix 1, Table 25)2025-08-07GPT-5 System Card (OpenAI, August 2025)

StrongReject — not_unsafe by category (OpenAI policy graders) — illicit/non-violent-crime prompts

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-oss-120b0.979not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); developer-reported (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)
gpt-oss-20b0.960not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); developer-reported (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)
o4-mini0.980not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); reported by OpenAI in the gpt-oss model card (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)

StrongReject — not_unsafe by category (OpenAI policy graders) — violence prompts

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-oss-120b0.983not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); developer-reported (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)
gpt-oss-20b0.979not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); developer-reported (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)
o4-mini0.991not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); reported by OpenAI in the gpt-oss model card (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)

StrongReject — not_unsafe by category (OpenAI policy graders) — abuse/disinformation/hate prompts

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-oss-120b0.993not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); developer-reported (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)
gpt-oss-20b0.982not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); developer-reported (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)
o4-mini0.982not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); reported by OpenAI in the gpt-oss model card (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)

StrongReject — not_unsafe by category (OpenAI policy graders) — sexual-content prompts

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
gpt-oss-120b0.989not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); developer-reported (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)
gpt-oss-20b0.970not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); developer-reported (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)
o4-mini0.974not_unsafe under OpenAI policy graders; known jailbreaks inserted into safety refusal prompts (not the goodness@0.1 metric); reported by OpenAI in the gpt-oss model card (card §4.2 (Table 6))2025-08-05gpt-oss-120b & gpt-oss-20b Model Card (OpenAI, August 2025)

StrongReject — Compliance rate (xAI)

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
Grok 4.51.5%high thinking effort; compliance on the StrongREJECT suite, lower is better; production safeguards; developer-reported (card §9.1)2026-08-12Grok 4.6 Model Card (xAI, August 2026)
Grok 4.63.9%high thinking effort; compliance on the StrongREJECT suite, lower is better; production safeguards; developer-reported (card §9.1)2026-08-12Grok 4.6 Model Card (xAI, August 2026)

StrongREJECT v2 — Attack success rate, full cascaded pipeline (multi-turn LLM attacker)

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
Muse Spark44.6accumulated ASR after five attack stages; lower is better; developer-reported (card §Table 2 / Fig. 27 (§3.1.1))2026-05-26Muse Spark Safety & Preparedness Report (Meta, May 2026)
Meta AI Thinking52.0deployed system; developer-reported (card §Fig. 27 (§3.1.1))2026-05-26Muse Spark Safety & Preparedness Report (Meta, May 2026)
GPT-5.437.6reported by Meta in the Muse Spark report (card §Table 2 / Fig. 27 (§3.1.1))2026-05-26Muse Spark Safety & Preparedness Report (Meta, May 2026)
Claude Opus 4.631.7reported by Meta in the Muse Spark report (card §Table 2 / Fig. 27 (§3.1.1))2026-05-26Muse Spark Safety & Preparedness Report (Meta, May 2026)
Gemini 3.1 Pro81.7reported by Meta in the Muse Spark report (card §Table 2 / Fig. 27 (§3.1.1))2026-05-26Muse Spark Safety & Preparedness Report (Meta, May 2026)

StrongReject — not_unsafe (OpenAI system cards)

Results as printed in developer system cards, model cards and technical reports; each row's Setting records the developer's stated conditions and the document section.

ModelScoreSettingDateSource
o30.97not_unsafe; higher is better; developer-reported (card §3.2, Table 3)2025-04-16OpenAI o3 and o4-mini System Card (April 2025)
o4-mini0.96not_unsafe; higher is better; developer-reported (card §3.2, Table 3)2025-04-16OpenAI o3 and o4-mini System Card (April 2025)
o10.97not_unsafe; higher is better; comparison model; reported by OpenAI in the o3 and o4-mini system card (card §3.2, Table 3)2025-04-16OpenAI o3 and o4-mini System Card (April 2025)

Interpreting scores

The raw StrongREJECT score is a 0–1 measure of harm delivered, so lower is safer; goodness@0.1 inverts it, so higher is safer. The two must not be compared, and neither can be compared with a percentage reported under an unstated convention.

The benchmark's size sets a precision limit the authors state explicitly. With 313 prompts, a jailbreak's effectiveness can be estimated "to within 0.05 points on a 0-1 scale with 90% confidence in the worst case," and they give the calculation. They also state the corresponding limitation directly: "while useful for jailbreak algorithm developers who need to evaluate their attacks frequently during development, StrongREJECT's 313-prompt dataset is not large enough to be a stand-alone, definitive measure of model robustness," and recommend that developers seeking a comprehensive view complement it with larger-scale analyses A StrongREJECT for Empty Jailbreaks (Souly et al., 2024).

The willingness–capabilities tradeoff is the paper's most consequential interpretive finding, and it was established by two experiments designed to isolate capability from willingness. In the first, the 37 jailbreaks were applied to Dolphin, an unaligned model that answers forbidden prompts regardless, so any variation in score must come from the jailbreak's effect on capability; the jailbreaks that most raised aligned models' willingness most reduced Dolphin's scores. In the second, jailbreak transformations were applied to benign MMLU questions and fed to GPT-4o, scored on a 171-question MMLU subset; again, the jailbreaks that most raised willingness most reduced MMLU accuracy. The authors conclude that "jailbreaks generally harm model capabilities, making responses less coherent, less on-topic, less realistic/factual, less detailed, or otherwise lower quality," which is also their explanation for why earlier evaluators were upward-biased: those evaluators credited willingness without checking capability A StrongREJECT for Empty Jailbreaks (Souly et al., 2024).

Autograder error is a live source of noise, on the evidence of the people running it. Reviewing the cross-lab exercise, OpenAI writes that after manual review "the majority of the apparent quantitative distinction between the slightly lower quantitative performance of Opus 4 and Sonnet 4 compared to OpenAI o3 and o4-mini is actually the result of errors in the auto-grader rather than an actual difference in model quality," while noting the lower robustness of GPT-4o and GPT-4.1 remained clear. It adds that "constructing fully reliable graders is a fundamentally hard problem" and that researchers should inspect results directly (Source: openai.com).

Limitations and criticism

The paper lists three limitations: the scope is text-only LLMs, so its applicability to multimodal models is unclear; the prompt set depends on providers' terms of service, which change, with the authors citing OpenAI lifting its prohibition on military applications as an example; and the dataset is small relative to benchmarks such as MMLU's 15,908 questions.

Saturation is the criticism that has emerged in use. OpenAI's GPT-5.2 system card update states that the original set was "otherwise highly saturated" and that it moved to a filtered adaptation, reporting that gpt-5.2-thinking outperformed gpt-5.1-thinking while gpt-5.2-instant regressed against gpt-5.1-instant, and attributing part of that gap to grader issues with "the remainder appear[ing] to be a regression in some cases under the illicit category" (Update to GPT-5 System Card: GPT-5.2 (OpenAI, December 2025)). The clustering of the Thinking Machines figures between 97.4% and 99.8% points the same way.

A separate limitation is inherited rather than intrinsic: the same paper's finding that jailbreak effectiveness is overstated elsewhere means StrongREJECT scores will generally be lower than those published alongside new attacks, so cross-paper comparisons of attack success rates remain unreliable unless the evaluator is held constant.

Use in policy and safety frameworks

StrongREJECT is the academic jailbreak benchmark OpenAI reports most consistently. It appears in the o1 system card, where goodness@0.1 rose from 0.22 for GPT-4o to 0.83 for o1-mini and the card states "the o1 family significantly improves upon GPT-4o, especially on the challenging StrongReject evaluation" (Source: arxiv.org); in the GPT-4.5 system card, where the score fell back to 0.34 (OpenAI GPT-4.5 System Card (February 2025)); and in the GPT-5.2 system card update in filtered form (Update to GPT-5 System Card: GPT-5.2 (OpenAI, December 2025)). Ahead of the GPT-5.4 launch in March 2026, OpenAI replaced its StrongReject-based jailbreak benchmark with a more challenging multi-turn evaluation derived from red-teaming exercises, in which attacker strategies probe, adapt and escalate over the course of a conversation, reporting worst-case defender success rate (GPT-5.4 Thinking System Card).

It is also the metric on which deliberative alignment rests. OpenAI's deliberative-alignment paper reports that o1 models "advance the Pareto frontier of refusing to answer malicious jailbreak prompts (from StrongREJECT) and not over-refusing benign prompts (from XSTest)" relative to GPT-4o and other models, with error bars from 1,000 bootstrap trials (Deliberative Alignment: Reasoning Enables Safer Language Models (Guan et al., OpenAI, 2024)).

The benchmark crossed lab boundaries in August 2025, when OpenAI and Anthropic ran evaluations on each other's models and used StrongREJECT v2 as the jailbreak-resistance test. OpenAI reported that the reasoning models — o3, o4-mini, Claude Opus 4 and Claude Sonnet 4 — were generally robust, that GPT-4o and GPT-4.1 were more susceptible, and, qualitatively, that Claude Sonnet 4 and Opus 4 were most vulnerable to the "past tense" jailbreak while o3 resisted it; it also noted that apparent robustness to low-resource-language attacks such as Guaraní "appeared to be due to lack of linguistic comprehension rather than specific robustness" (Source: openai.com).

Open-weight developers report it in model cards: Thinking Machines Lab publishes StrongREJECT alongside FORTRESS for Inkling and Inkling-Small (Inkling Model Card (Thinking Machines Lab, July 2026)). It is also used in alignment research as a discriminator between phenomena: Betley et al.'s emergent-misalignment paper compares a jailbroken GPT-4o with an insecure-code fine-tuned model and finds the jailbroken model more likely to accept harmful requests on StrongREJECT while the insecure-code model more often produces misaligned content unprompted, concluding the two are distinct phenomena (Emergent Misalignment: Narrow Finetuning Can Produce Broadly Misaligned LLMs (Betley et al.)).

Relationships

See also