**FYI: malicious actors could likely hijack your grok build sessions during the month of june by simply prompting 'hi'**

Reddit r/ArtificialInteligence News

Summary

A critical security flaw in Grok's build sessions was discovered, where a simple 'hi' prompt could hijack sessions and access other users' workspaces due to failed session isolation.

This is serious because it is not a chatbot making up a story. A stateless "hi" with tools: [] still came back finish_reason: tool_calls and executed read_file/grep on another user's workspace. That means session isolation failed at the serving layer: one tenant's context was reachable from another. If that happens, a prompt as empty as "hi" can pull someone else's files, tools, and private session. Closing it as a hallucination, then deprecating the model, does not prove the mix-up cannot happen on whatever replaced it.
Original Article

Similar Articles

@elonmusk: Grok Build updates

X AI KOLs Timeline

Grok Build v0.2.114 introduces a /delete command to remove session history and improves startup reliability on constrained hosts.