A clean-looking later request can reactivate instructions stored during an earlier task. The authors distinguish immediate, autonomous and latent behavior, and report persistence across five intervening rounds conditional on successful planting. This conditional result is not an unconditional deployment attack rate. Mechanism, preconditions and effects. Car…
Inspect the ClaimsCase · DiggingBeagle record
Carryover isolates the planting and later activation of persistent agent injection
Controlled evaluation of persistent agent state and selected harness defenses.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- not applicable
- AI role
- AGAINST AI
Basis and provenance
CLM-CARRYOVER reports: Carryover evaluates persistent injection across 101 tasks and 12 scenarios, separating the turn that plants malicious state from later turns that trigger it. Source SRC-2026-RADAR-CARRYOVER is located at 'Abstract, benchmark design and persistence analysis'. The distinctive mechanism begins: CarryoverBench separates an attacker's initial insertion into persistent memory or a scheduled heartbeat task from the later activation of that content. Classification: setting=evaluation, exploit_status=demonstrated, evidence_grade=B on the bounded original investigator/vendor or paper evidence, without independent dynamic replication. remediation_status=not_applicable; scoped control or limit: Treat persisted instructions as untrusted, revalidate the author and intended permissions on each reload, and gate autonomous scheduled effects independently from the text that requested them. A later agent turn must not inherit irrevocable authority merely because a file survived. The null impact band avoids an ungrounded cross-Case severity rating; observed damage, targeted population and controlled test outcomes cannot be exchanged as the same quantity. Where a patch is described, its availability is separate from independently tested effectiveness.
Assessed Oct 23, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-CARRYOVER · Carryover preprint, arXiv 2610.28425v1
At a glance
No independent rerun, production incidence estimate or universal persistence guarantee.
Limits and uncertaintyFull account
A clean-looking later request can reactivate instructions stored during an earlier task. The authors distinguish immediate, autonomous and latent behavior, and report persistence across five intervening rounds conditional on successful planting. This conditional result is not an unconditional deployment attack rate.
Mechanism, preconditions and effects. CarryoverBench separates an attacker's initial insertion into persistent memory or a scheduled heartbeat task from the later activation of that content. The dataset contains 101 attack tasks across twelve personal-assistant scenarios, with instant, autonomous and latent trigger channels. Conditional on a successful planted state, the researchers report little measurable decay in activation across five follow-up rounds; porting the latent channel to Hermes reduced but did not eliminate it.
Comparison and evidence limits. Planting success and trigger success have different denominators, and a trigger working for five synthetic follow-ups does not demonstrate unlimited persistence. This distinction also matters for shared-memory effects, where a second user's authority becomes relevant in addition to session boundaries.
Timeline
- Oct 20, 2026disclosure
Public disclosure
Claims & evidence
CLM-CARRYOVERCarryover evaluates persistent injection across 101 tasks and 12 scenarios, separating the turn that plants malicious state from later turns that trigger it.supported
Basis: reported finding
- supportsCarryover preprint, arXiv 2610.28425v1primary disclosure
Abstract, benchmark design and persistence analysis
Controls and mitigations
- Treat persisted instructions as untrusted, revalidate the author and intended permissions on each reload, and gate autonomous scheduled effects independently from the text that requested them. A later agent turn must not inherit irrevocable authority merely because a file survived.
Unknowns and contradictions
- No independent rerun, production incidence estimate or universal persistence guarantee.
Sources and citation
Material revision history
- Oct 23, 2026 · Canonical change recorded · new in release · revision 183