Open-source attack tools generate variants, run multi-turn strategies that escalate over several turns, and refine prompts against a judge model until they get through.
OWASP's 2026 list recommends that defences be tested "against adaptive attackers who have read the deployed defense", and that static-only attack-success claims be rejected. It cites research (Nasr et al., 2025) that found attack success near zero for static attacks, but above 90% for adaptive ones against most of 12 recent defences.
We follow that recommendation as far as you disclose your defences, and the report lists which were disclosed and tested. Public baselines such as AgentDojo and JailbreakBench run only if the written scope adds them.
Public benchmarks measure models and defences on their own tasks. A count from your app, on your sources and your rendering, is a different measurement, and neither stands in for the other.
People still decide which attacks matter for your app, how to chain a hidden instruction through your sources into something your chat window will render, and what a success would cost you. Severity comes from that judgement, never from frequency alone.