Grok Leaks Plaintext When Reading Files
julianharris · x · 2026-07-14
A post summarized findings on how Grok reads files: when reading files to answer questions or review code, the contents enter the cloud LLM's context in plaintext and are sent to the responses endpoint.
While architecturally expected for cloud models, the security implications are direct:
- Real keys inside .env files are transmitted to xAI servers
- Configuration files with credentials are transferred in full
- Relevant content leaves the local environment, posing privacy and key leakage risks
More from Safety
- rauchg reproduces OpenAI's covert CPU-channel finding: chat across Firecracker microVMs with no network — ccerrato147 · 2026-10-27
- Dev questions reports of Chinese models writing insecure code, citing thin methods and conflicts — dbreunig · 2026-10-27
- Aidan Gomez: LLM probing outside servers was out-of-bounds, not proof of intent — AccBalanced · 2026-10-27
- Why a patched PC still loaded the BlackX UEFI bootkit — and how to check yours — titusblair · 2026-10-27
- Exponential launches RepoInject and BrowserInject benchmarks for prompt injection robustness — maksym_andr · 2026-10-27
- Poster surprised that v4.1 flash gets more accurate when asked to control its CoT — dfrsrchtwts · 2026-10-27