A Public ChatGPT Share Link Could Run JavaScript and Read Private Chats

Security firm Parameter found that a public ChatGPT share link could execute attacker JavaScript in a signed-in visitor’s session and read that person’s private conversations. OpenAI fixed both web front ends on October 26, 2026, nine days after the report.

Christopher Ort
By Christopher Ort · 2 min read
Share
A cafe table with a laptop half-open and a phone face down, late daylight, no readable screen content.
On this page
  1. Quick Take
  2. What happened
  3. What you should do
  4. What it means
  5. About the analysis
  6. Sources

A shared ChatGPT conversation is supposed to be a read-only postcard, not a way into someone else’s private threads. The Injection and later coverage of Parameter‘s research describe a bug in which “a public ChatGPT share link could run attacker JavaScript as chatgpt.com in any signed-in visitor’s session and read their private conversations.” OpenAI “fixed both web frontends on October 26, nine days after Parameter reported it,” and classified the issue as P1, according to contemporaneous reporting.

i10X Quick Take

Quick Take

  1. What: A malicious public share link could escape its preview sandbox, run JavaScript as the ChatGPT origin, and read a signed-in visitor’s private chats.
  2. Reported: Parameter disclosed the issue to OpenAI in mid-October 2026.
  3. Fixed: October 26, 2026, on both web front ends.
  4. Status: Patched. There is no user update to install. Be cautious with old, untrusted share links from before the fix, as you would with any unexpected URL.

What happened

ChatGPT’s public share pages render conversation content, including mathematical notation and other rich HTML, in a preview that is supposed to stay sandboxed. Parameter’s write-up, as described in follow-on coverage, traces a chain through a permissive message listener in MathLive and raw HTML keyboard-layout data that let script run with the privileges of chatgpt.com. Once that happened, a visitor who was already signed in could have private conversations read by the attacker who crafted the shared link.

This is a different bug from Check Point’s Lockdown Mode bypass, which OpenAI had already patched in September by tightening iframe popup permissions. Both are sandbox escapes around ChatGPT’s web preview, and both are now closed.

What you should do

  • No patch is required on the user side; OpenAI deployed the fix on October 26.
  • If you clicked untrusted ChatGPT share links while signed in before that date, there is no public evidence in these reports that your account was targeted, but it is reasonable to review account sessions and treat unexpected shared links like unexpected email attachments.
  • This is a reminder to open unfamiliar share links in a separate browser profile, or while signed out, especially when they come from strangers.

What it means

“Share this chat” is a distribution channel. If the shared page can run script as the product origin, it becomes an account-takeover and data-exfiltration path for anyone who can talk a signed-in user into clicking. OpenAI’s nine-day fix window and P1 classification match the severity. Combined with the Lockdown Mode research published in November, it has been a rough season for ChatGPT’s preview sandboxes — and a good argument for treating those previews as an attack surface, not as a cosmetic feature.

About the analysis

Researched and written with AI assistance under the editorial responsibility of the i10X News team. The title image is an AI-generated illustration. Read our AI Use Policy. Spotted an error? Request a correction.

This i10x report is based on Parameter’s public research post, The Hacker News’ October 2026 coverage, and The Injection’s week-44 summary. i10x did not reproduce the share-link escape.

Sources

Christopher Ort

Christopher Ort

Christopher Ort handles SEO, AI agent workflows and PR & partnerships at i10x.ai, the all-in-one AI workspace built by i10X Global Pte. Ltd. in Singapore. He is a graduate of Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU). He is the author of “The Style Penalty”, a study published on SSRN that analyses 1,576 evaluation decisions by four frontier AI models to show how AI-written CVs fare in automated hiring screens; the research has been covered by heise online and t3n.

Timeline

What happened before

  1. Release

    GPT-6.1 Terra

    1.05M context · $1 / $5 per 1M tokens

    openai.com (source, opens in a new tab)
  2. Release

    GPT-6.1 Sol

    1.05M context · $2 / $10 per 1M tokens

    developers.openai.com (source, opens in a new tab)
  3. Release

    GPT-6 Sol & Luna

    1.05M context · $2 / $10 per 1M tokens

    Two GPT-6 reasoning models. Price shown is GPT-6 Sol (≤272K prompt); GPT-6 Luna costs $0.10 / $0.50.

    developers.openai.com (source, opens in a new tab)
  4. Release

    GPT-6 Astra

    1.05M context · $10 / $50 per 1M tokens

    OpenAI's most capable model for reasoning, coding, computer use and research.

    openai.com (source, opens in a new tab)
  5. Release

    GPT-5.6

    1.05M context · $4 / $20 per 1M tokens

    GPT-5.6 family: Sol (frontier), Terra (balanced) and Luna (high-volume).

    developers.openai.com (source, opens in a new tab)
Full ChatGPT timeline ›

Editor's picks

  1. CVE-2026-77604: Path Traversal Vulnerability in Code Graph RAG MCP Server Allows Arbitrary File Read
  2. CVE-2026-123271: ChatCLI OAuth Flaw Allows Token Theft via Malicious MCP Servers
  3. CVE-2026-123022: AgentScope MCP Workspace Allows Unauthenticated Remote Code Execution
  4. CVE-2026-97677: Path Traversal Flaw in IBM Langflow OSS 1.0.0–1.12.2 Allows File Read/Write
  5. Active Support DoS Flaw Lets Unauthenticated Attackers Crash Rails Servers via Action Cable