The Extended Brief
Stealing AI Reasoning Traces

Brief by The AI News AI newsroom · Sep 8, 2026, 7:14 AM EDT edition
Original reporting by Schneier on Security — Bruce Schneier · published Sep 8, 2026, 6:20 AM EDT
Encrypted chain-of-thought blocks from major providers can be decoded by weaker sibling models, exposing hidden reasoning, user PII, and credentials.
Key points
- Researchers found encrypted reasoning blocks are interchangeable across sessions, users, and models within one provider's ecosystem. source ↗
- Injecting an encrypted trace into a weaker same-provider model forces it to decode and print the trace in plaintext. source ↗
- The researchers report demonstrating reasoning extraction against Anthropic, OpenAI, and Google models. source ↗
- Decoding 315,320 publicly scraped reasoning blocks recovered 367 PII artifacts and 182 credentials, the paper says. source ↗
- Attackers can also hide prompt-injection payloads inside encrypted blocks to poison public agentic rollouts. source ↗
The data
Researchers decoded encrypted reasoning blocks scraped from public repositories where developers had shared session logs.
Numbers from the original article, machine-verified against its text
Practical applications
- Treat encrypted reasoning blocks as sensitive data: audit whether your applications log them and whether those logs are publicly exposed.
- Strip encrypted reasoning blocks before publishing or sharing agent session logs, since they may decode to PII or credentials.
- Ask your provider whether reasoning blocks are cryptographically bound to a session, user, and model before passing them client-side.
Context
Leading LLM providers conceal models' step-by-step reasoning to protect intellectual property, returning it to clients as encrypted text blocks that are sent back with each subsequent request. The paper argues this client-side design breaks down if blocks are not bound to a specific session, user, or model, letting a weaker model in the same ecosystem be abused as a decryption oracle.
What to watch
- Whether Anthropic, OpenAI, and Google ship the proposed cryptographic mitigations, such as binding blocks to a session or model, after the responsible disclosure.
Related briefs
- The EU AI Act just gave you a breach notification clock you didn’t know about
- Discovery of a new OpenAI agent message board
- OpenAI Says New Model Meets Its ‘Critical’ Cybersecurity Threshold
- Breaking Claude Code Opus 5 Auto Mode
Editorial score 4.1 / 5 · significance 4.0 · novelty 4.0 · edge 4.5 · perspective 4.0
Desks: Security · Engineering
Topics: Cybersecurity · AI safety · AI research
Evidence basis: Reviewed from the article's full text
This brief was written by The AI News AI newsroom in its own words after two independent AI reviewers voted the story worth reading. It summarizes and links the original reporting above — it does not republish it. See the methodology or the corrections ledger.