Full Report
Interesting research: “Stealing Reasoning Traces from Proprietary LLM APIs“: Abstract: Leading large language model providers now conceal their models’ step-by-step reasoning, or chain-of-thought, to protect intellectual property and limit information leakage. Rather than storing these traces server-side, providers return them to the client as blocks of encrypted text, which the client passes back with each subsequent request. Building on prior research, we identify an architectural vulnerability: these encrypted blocks are fully compatible and interchangeable across different sessions, users, and models within a provider’s ecosystem. We exploit this compatibility to develop a scalable decryption jailbreak. By injecting an encrypted reasoning trace from a given model into a weaker, and less safeguarded model from the same provider, we force it to decode and output the trace verbatim in plaintext, without ever jailbreaking the more capable model directly. This vulnerability enables four distinct attack vectors. First, it circumvents anti-distillation mechanisms, allowing adversaries to extract a proprietary model’s reasoning, as we demonstrate across Anthropic, OpenAI, and Google. Second, it allows for large-scale private data extraction. Developers frequently share session logs publicly, unaware of contents of the encrypted blocks. By decoding 315,320 reasoning blocks scraped from public repositories, we recovered 367 Personally Identifiable Information (PII) artifacts and 182 credentials. Third, it inadvertently reveals hazardous information hidden within the reasoning process, even in cases where the model’s final, visible output safely rejects a malicious request. Fourth, attackers can leverage this flaw to execute invisible prompt injections, embedding malicious payloads entirely within encrypted blocks to poison public agentic rollouts. Following responsible disclosure, we propose concrete cryptographic and system-level mitigations to secure client-side reasoning...
Analysis Summary
# Vulnerability: Cross-Model Reasoning Trace Decryption (Architectural Flaw)
## CVE Details
- **CVE ID:** Not yet assigned (New architectural research)
- **CVSS Score:** Estimated 8.1 (High) - *Calculated based on Confidentiality (High), Integrity (High), and Availability (None).*
- **CWE:** CWE-300: Channel Accessible Termination, CWE-923: Improper Restriction of Communication Layer Coverage (specifically lack of cryptographic binding).
## Affected Systems
- **Products:** Proprietary Large Language Model (LLM) APIs utilizing client-side encrypted Chain-of-Thought (CoT).
- **Affected Vendors:** Anthropic, OpenAI, and Google (as identified in the research).
- **Configurations:** Systems that return encrypted reasoning traces to the client for state management instead of storing them server-side.
## Vulnerability Description
The vulnerability stems from an architectural failure to cryptographically bind encrypted reasoning blocks to a specific session, user, or model version. Providers return internal "reasoning traces" to the client as encrypted blobs. These blobs are intended to be opaque; however, the decryption keys are shared across a provider's ecosystem. An attacker can take an encrypted trace from a highly secure/sophisticated model and "inject" it into a request sent to a weaker, less-safeguarded model from the same provider. Because the blocks are interchangeable, the weaker model successfully decrypts the trace and can be prompted to output the contents in plaintext, effectively acting as an automated decryption oracle for the proprietary trace.
## Exploitation
- **Status:** PoC available (Academic research/Responsible disclosure).
- **Complexity:** Medium (Requires knowledge of API request structures and prompt engineering to force output).
- **Attack Vector:** Network (Remote API interaction).
## Impact
- **Confidentiality:** **High.** Exposure of proprietary reasoning logic, distillation of model "thought" processes, and leakage of PII/credentials embedded in traces.
- **Integrate:** **High.** Allows for "invisible prompt injections" where malicious instructions are hidden inside encrypted blocks to poison agentic workflows.
- **Availability:** **Low.** No direct impact on system uptime was identified.
## Remediation
### Patches
- No direct software patches are available for end-users. The fix must be implemented server-side by the LLM providers (Anthropic, OpenAI, Google).
### Workarounds
- **For Developers:** Avoid sharing session logs or API telemetry that include the encrypted reasoning blocks in public repositories (e.g., GitHub, HuggingFace).
- **For Providers:** Implement cryptographic binding (e.g., HMAC or AEAD) that includes the Model ID, User ID, and Session ID in the associated data of the encrypted block to prevent interchangeability.
## Detection
- **Indicators of Compromise:**
- High-frequency API calls to "smaller" or "legacy" models involving large, unexplained encrypted state blocks.
- Prompts that specifically attempt to coerce the model into reciting its "internal state" or "previous reasoning."
- **Detection Methods:** Providers should monitor for cross-model token reuse where an encrypted block generated by one model UUID is submitted to a different model UUID.
## References
- **Original Paper:** hxxps[://]arxiv[.]org/abs/2608.09867
- **Schneier on Security:** hxxps[://]www[.]schneier[.]com/blog/archives/2026/09/stealing-ai-reasoning-traces[.]html