WeSearch

Multi-turn jailbreak rates across 15 frontier models (Grok 88%, Claude 12%)

Nicholas Conley, Amy Chang· ·7 min read · 0 reactions · 0 comments · 33 views
Multi-turn jailbreak rates across 15 frontier models (Grok 88%, Claude 12%)
TL;DR · WeSearch summary

A recent evaluation of 15 frontier large language models (LLMs) reveals that single-turn attack success rates are not reliable indicators of multi-turn vulnerabilities. The study found multi-turn attack success rates ranging from 7.89% to 88.30%, indicating significant risks across all models tested. This highlights the need for more comprehensive evaluation methods that account for iterative adversarial behavior.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
Cisco Blogs · Nicholas Conley, Amy Chang
Read full at Cisco Blogs →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherCisco Blogs
Canonical URLhttps://blogs.cisco.com/ai/proprietary-problems
Publication timeWed, 27 May 2026 22:23:18 +0000
Retrieval time2026-05-27T22:38:06.181Z
Last seen2026-05-27T22:38:06.181Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterAyPlJ8ZJoiWU
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

May 27, 2026 Leave a Comment Artificial Intelligence - AI Proprietary Problems: No Frontier Model Is Multi-Turn Immune6 min read Nicholas Conley, Amy Chang The dominant safety benchmarks for frontier large language models (LLMs) share a structural assumption: that a single prompt and a single model response are enough to characterize how a model behaves under adversarial attack. These benchmarks inform model cards, safety reports, and procurement decisions across the industry, but they all only measure one narrow slice of attacker behavior.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Cisco Blogs.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Cisco Blogs