R2ECAP constructs a malicious earlier reasoning trace and a later seemingly legitimate continuation whose cached token representations retain that influence. When downstream queries reuse the conditioned KV cache, the initial malicious text may have been removed from the user-visible context but can still steer generation. This moves the trust problem away…
Inspect the ClaimsCase · DiggingBeagle record
Discarded malicious reasoning influences later answers through reused KV cache
R2ECAP preserves attacker influence in derived cache state even when the initial poisoning text is no longer visible.
Controlled experiments across three open-weight models, October 2026; no verified commercial tenant compromise.
Assessment profile
Assessment method- Setting
- research demonstration
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- not applicable
- AI role
- AGAINST AI
Basis and provenance
Technical report or researcher-controlled experiments document the stated mechanism, but independent reproduction and population-wide prevalence are not established. Impact band is left unassigned because no calibrated damage threshold or representative victim impact is supported by the available record.
Assessed Oct 20, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-R2ECAP-RATES · CLM-R2ECAP-MECHANISM · R2ECAP: Stealthy poisoning via reused reasoning KV cache
At a glance
Cache reuse is an authorization and provenance decision whenever future workloads may inherit state from an earlier untrusted interaction.
Read the implicationsNo demonstrated cross-tenant attack on commercial infrastructure. Impact of actual eviction policies, prefix caching variants and isolated cache keys remains to be measured.
Limits and uncertaintyFull account
R2ECAP constructs a malicious earlier reasoning trace and a later seemingly legitimate continuation whose cached token representations retain that influence. When downstream queries reuse the conditioned KV cache, the initial malicious text may have been removed from the user-visible context but can still steer generation. This moves the trust problem away from the text retained in the prompt to the lineage of a derived inference artifact.
The paper reports up to 79% success for exact-query cache reuse and 16% to 46% for cross-query reuse across three tested open-weight models. These are chosen laboratory setups; commercial cross-user caching and a real tenant isolation failure are not established. Clearing visible text alone is insufficient if derived state remains reachable; cache lineage and invalidation behavior become part of the security model.
Deleting the triggering text from the visible prompt does not necessarily remove derived KV states made from that text. In the tested cache-reuse scheme, later queries inherit a contaminated representation even without replaying the original malicious sentence. The paper distinguishes exact-cache, cross-query and retrieval modes; their success rates should not be pooled or inferred as a measured cross-tenant commercial leak.
Timeline
- Oct 19, 2026disclosure
Public disclosure
Claims & evidence
CLM-R2ECAP-RATESThe paper reports attack success up to 79% in exact-cache reuse, 16 to 46% in cross-query reuse and 46% in a tested reasoning-trace retrieval setting.supported
Basis: reported finding
- supportsR2ECAP: Stealthy poisoning via reused reasoning KV cacheprimary disclosure
Abstract; Section 1 Contributions; evaluation table on cache-reuse settings
CLM-R2ECAP-MECHANISMThe study demonstrates residual influence of an earlier attacker-shaped reasoning trace through subsequent KV cache reuse after the visible trace is removed.supported
Basis: reported finding
- supportsR2ECAP: Stealthy poisoning via reused reasoning KV cacheprimary disclosure
Introduction; Threat Model; Method
Implications
Cache reuse is an authorization and provenance decision whenever future workloads may inherit state from an earlier untrusted interaction.
Unknowns and contradictions
- No demonstrated cross-tenant attack on commercial infrastructure.
- Impact of actual eviction policies, prefix caching variants and isolated cache keys remains to be measured.
Sources and citation
Material revision history
- Oct 20, 2026 · Canonical change recorded · new in release · revision 177