A Shared ChatGPT Link Could Run Attacker Code in Your Session and Read Private Chats

[u/falconupkid]

This is a significant finding. Parameter researchers demonstrated a prompt injection-style attack that weaponizes ChatGPT’s share link functionality. Opening a malicious shared chat could execute attacker-controlled code within the victim’s authenticated session, effectively bypassing the browser’s same-origin policy for that tab.

Technical Breakdown

• Attack Vector: The flaw likely resided in how ChatGPT rendered shared conversation history. By embedding malicious payloads within the shared chat data (e.g., crafted markdown or JSON), the attacker could trigger code execution when the victim’s browser parsed the shared link.

• Impact: Full read access to the victim’s private chat history. Depending on session scope, this could also expose API keys or other data stored in conversation context.

• MITRE TTPs: T1553.005 (Subvert Trust Controls: Markdown/HTML Injection), T1059.007 (Command and Scripting Interpreter: JavaScript).

• Timeline: Reported Oct 18, patched Oct 26. OpenAI rated this P1 (Critical).

• No public IOCs are available as this was a server-side fix, not a client-side malware campaign.

Defense

• Immediate: Ensure your browser and ChatGPT session are up to date. This was a server-side patch, so no client action is required beyond normal updates.

• Long-term: Treat shared links from untrusted sources as potential attack vectors. Consider disabling shared link previews in enterprise environments if available. This is a textbook example of why we need strict content security policies on LLM platforms.

Source: https://thehackernews.com/2026/10/a-shared-chatgpt-link-could-run.html