Incident tracker
Security incidents and advisories
This tracker records publicly disclosed security incidents at confidential-inference providers and security advisories against the TEE, GPU and firmware layers they rely on. Every row cites a primary source (post-mortem, bulletin, advisory, release or commit). Text records what the source says, attributed and dated. Actions need a link; a promise is not an action. Empty fields stay empty. Absences are never findings.
Provider incidents
| Disclosed | Incident · who | Layer | Window | What the source says | What was done | User action | Sources |
|---|---|---|---|---|---|---|---|
| MiniMax-model requests forwarded to MiniMax by AtlasCloud, Novita and StreamLakeOpenRouter (router), Novita, AtlasCloud, StreamLake, MiniMax | Router | Novita: 2026-05-28 to 2026-11-11 (its own MiniMax requests, direct and via OpenRouter) | Dragos (Nov 19) seeded about two million prompts with unique URLs and canary credentials from July to November and reports prompts reaching parties other than the provider called. OpenRouter (Nov 22) says researchers showed some providers' data policies were not upheld and that the findings showed no breach of OpenRouter. Novita (Nov 22) says a routing configuration issue sent some MiniMax requests to MiniMax's official API instead of Novita-hosted infrastructure, and that request contents may have been accessed or retained by a third party. | Novita: if requests to its MiniMax models in the window held live credentials, API keys or other secrets, revoke or rotate them. | |||
| Together AI: stored prompt samples downloaded after a credential leaked to a public repoTogether AI | Stored data | Samples from requests to MiniMax M3, GLM-5.2 and Kimi K2.6, mainly on 2026-06-24, 07-04, 07-08 and 07-14 | Together says prompt samples collected for software testing sat in a private Hugging Face repository. An AI coding agent committed a credential for it to Together's public xorl GitHub repository; an unauthorized party used it to download the samples and tested credentials found in them, five of which were Dragos canaries. | Together: customers handling sensitive prompt data should enable ZDR in account settings. | |||
| Phala: in-flight requests visible on one unhardened inference VM (DeepSeek V4 Flash 0731 via OpenRouter)Phala | Platform | 2026-10-21 00:00 to 2026-11-08 05:35 UTC | Phala's preliminary report says an attacker reached internal management interfaces on Oct 21, planted malware and took application credentials; a new GPU server was "serving production traffic without our full production security hardening", making in-flight request data visible during processing. Phala says it was contained at 05:35 UTC on Nov 8. The report calls the DeepSeek box an "inference VM" and does not say whether it ran in a TEE. | Phala: treat DeepSeek V4 Flash 0731 requests OpenRouter routed to Phala in the window as exposed and rotate any secrets in them. | |||
| Fireworks AI intrusion; Notion AI transcripts in a stored datasetFireworks AI, Notion (customer) | Stored data | October 2026 (bulletin updated 2026-11-09; Notion advisory 2026-11-12) | Fireworks says the attacker came in through a third-party cloud provider hosting development machines and reached account and billing data and, for some customers, stored secrets, datasets and partial model weights, and reports no impact to Inference (ZDR by default). Notion says a dataset held Notion AI chat transcripts used for Insights from under 1% of workspaces. |
| Notion: rotate credentials pasted into Notion AI. | ||
| NEAR AI Cloud: SGLang remote code execution on one inference serverNEAR AInear | Inference engine | 2026-11-08 (service paused; back by 2026-11-10 03:32 UTC) | NEAR says an RCE bug in SGLang gave the attacker code execution on one inference server; account details for about 100 users were downloaded, 18 legacy agents not running in its TEE were accessed, and two Cloud customers' API keys were in logs. NEAR: the attacker "could also have observed user requests being processed on the accessed server, including requests running in confidential mode." |
| |||
| Cloudflare Workers AI: other customers' request fragments in GLM 5.3 responsesCloudflare Workers AI | Inference engine | 2026-08-27 to 2026-09-09 | Cloudflare says 155 GLM 5.3 responses contained pieces of other customers' recent requests, all for prompts over 681,280 tokens: in split prefill/decode mode SGLang passed a rejected request to decode, which read KV cache pages still holding earlier data. Cloudflare says it found no evidence of deliberate exploitation. | ||||
| Phala Cloud: dstack guest-agent /logs endpoint leaked other tenants' environment variablesPhala Cloud (dstack) | Platform · TDX | 2026-10-08 to 2026-10-12 | Phala's post-mortem says a crafted container name on the guest-agent /logs endpoint (dstack OS images v0.3.1 to v0.6.0) returned container config including env vars, and a shared gateway admin token was used for 63 DNS-credential and ACME changes on one gateway. Phala says TEE and KMS keys, sealing keys, the on-chain KMS, customer disks and host SSH were not touched. | Phala: notified customers should rotate whatever was in their env vars. On dstack, check the OS image version and whether public_logs is on. |
TEE, GPU and firmware advisories
| Disclosed | Title | Hardware | What the source says | Fix / vendor position | Sources |
|---|---|---|---|---|---|
| DDRop: DDR5 interposer breaks memory integrity on TDX, Scalable SGX and SEV-SNP | TDX, SGX, SEV-SNP | A DDR5 RDIMM interposer (about $159 in parts at a build of 10) drops writes so stale ciphertext reads as current. On TDX it forces a victim TD into debug mode and forges an attacker TD's launch measurement; on SEV-SNP (EPYC Turin) it copies victim pages. Needs host control plus physical access. Presented at ACM CCS, Nov 18. | Intel and AMD treat physical DRAM attacks as out of scope; AMD-SB-3048 assigns no CVE and plans no mitigation. | ||
| Open Enclave SDK GHSA-2rx6-6737-vpgh: use-after-free gives a malicious host code execution in SGX enclaves | SGX | A use-after-free in the attester registry gives the host code execution in the enclave (critical). | |||
| NvRoot (CVE-2026-47591): NVIDIA driver bug gives a GPU container host root | NVIDIA | Stealthium says an unprivileged process in a GPU container can make the GPU write to read-only files and get host root, and that the R590, R575, R570 and older branches remain unpatched. | |||
| Mior (CVE-2026-0462, AMD-SB-3059): hypervisor redirects MMIO to break SEV-SNP integrity | SEV-SNP | AMD says coarse access control in SEV firmware lets a hypervisor redirect MMIO and break guest memory integrity (CVSS 5.9). Needs a malicious hypervisor and a modified BIOS; the researchers enable debug on a production CVM and forge attestation reports. |
Guests can refuse unpatched hosts in attestation: patched TCB[SNP] is 0x1F on EPYC 7003, 0x1E on 8004/9004, 0x8 on 8005/9005. | ||
| Skyfall (CVE-2026-40671, AMD-SB-3061): SEV-SNP guest registers leak via VMRUN error handling | SEV-SNP | AMD says incomplete cleanup in VMRUN error handling may leak SEV-SNP guest registers via a Transient Scheduler Attack (CVSS 4.9). Needs a malicious hypervisor. | |||
| AMD-SB-3064: Rowhammer alters the SEV-SNP reverse-map table with ECC off | SEV-SNP | Researchers used Rowhammer to alter the SEV-SNP reverse-map table with ECC disabled. | AMD says keep ECC on. | ||
| INTEL-SA-01520 (CVE-2026-42067): TDX Workload Attestation library accepted expired certificates | TDX | Intel's TDX Workload Attestation library before 0.2.0 accepted certificates outside their validity period (CVSS 5.9). |
| ||
| INTEL-SA-01580: 30 CVEs in the TDX Migration Trust Domain (MigTD) | TDX | Rated medium overall; three critical, including CVE-2026-61887 (9.4), a missing authentication step in SPDM rebind code. Intel says other TDX guests are not affected. | |||
| CVE-2026-119344 (Cocos AI): TEE evidence not bound to a platform owner or machine identity | TDX, SEV-SNP | Older Cocos versions accepted any valid TEE evidence with the right firmware and measurements "without binding the Evidence to an allowed platform owner or unique machine identity", allowing diversion to another genuine platform. The CVE text says it cannot be patched in source code alone. | Workaround per the advisory: allowlist hardware instance IDs (PIIDs on TDX). | ||
| EDK II GHSA-99cj-7hg9-mp4m: pre-boot RCE in the PXE network driver | A remote code execution bug in EDK II's PXE driver, the UEFI firmware many confidential VMs boot with. | ||||
| FABRICKED (CVE-2025-54510) and STALEUS (CVE-2025-54509): software-only SEV-SNP breaks | SEV-SNP | From ETH Zurich at USENIX Security 2026. FABRICKED needs control of UEFI firmware and the hypervisor and ends in guest read/write plus forged attestation reports; STALEUS needs hypervisor privileges and gets read/write inside a fully attested CVM. | Check that the attested TCB version carries AMD's fix. |