Check Point: A ChatGPT Lockdown Mode Bypass Allowed Silent Chat Exfiltration

Check Point Research discovered a vulnerability that bypassed ChatGPT Lockdown Mode, allowing silent exfiltration of chat history, phishing and malware delivery. In ChatGPT Classic the attack required no extra click. OpenAI deployed a fix on September 18, 2026; researchers published the details in November.

Christopher Ort
By Christopher Ort · 2 min read
Share
A closed laptop on a kitchen table beside a coffee cup, blinds half drawn, a faint glow on the lid, quiet morning light.
On this page
  1. Quick Take
  2. What happened
  3. What you should do
  4. What it means
  5. About the analysis
  6. Sources

OpenAI’s Lockdown Mode was supposed to be the extra-strict setting that stops prompt-injection exfiltration. Check Point Research found a way around it. In a paper published in early November 2026, the researchers say a vulnerability let attackers bypass Lockdown Mode and “perform covert exfiltration of chat data to an external server,” as well as phishing and malware delivery. In ChatGPT Classic, they write, “simply having a conversation is enough to trigger silent data exfiltration.”

i10X Quick Take

Quick Take

  1. What broke: Lockdown Mode, an optional ChatGPT setting meant to protect sensitive chats from prompt-injection exfiltration, could be bypassed.
  2. Impact: Silent theft of chat history, credential phishing, and malware delivery. The Hacker News quotes Check Point’s Eli Smadja saying the flaw included “zero-click data exfiltration in the ChatGPT desktop application.”
  3. How: After disclosure, OpenAI told Check Point on September 18, 2026 that it had deployed a fix by removing the allow-popups and allow-popups-to-escape-sandbox permissions from the outer HTML-preview sandbox iframe.
  4. Status: Check Point retested and says the technique no longer works. The public write-up arrived weeks after the fix.

What happened

Lockdown Mode was sold as a hardening switch: turn it on, and prompt-injection tricks that leak a conversation to an attacker’s server should fail. Check Point found that a popup could escape the HTML preview sandbox, taking those protections with it. Once the sandbox was bypassed, a crafted prompt, a malicious GPT, or a shared chat could be used to pull data out, or to push a phishing or malware payload.

The researchers say they disclosed the issue to OpenAI, which fixed the iframe permissions on September 18. That is a narrow, concrete change: popups were no longer allowed to leave the sandbox. Check Point confirmed the old technique stopped working after the change.

The Hacker News covered the research in November, after the fix was already in production. There has been no public statement from OpenAI or Check Point that this specific bypass was used in the wild before it was closed.

What you should do

  • No customer patch is required; the fix was deployed by OpenAI on September 18, 2026.
  • If you turned on Lockdown Mode because you handle sensitive data in ChatGPT, keep using it — the point of the research is that the mode was bypassed, then repaired, not that the mode is useless.
  • Treat older shared chats and untrusted GPTs from before mid-September with the usual caution. This report does not, by itself, prove that any particular chat was stolen.

What it means

Lockdown Mode is only as strong as the browser sandbox around HTML preview. A permission flag on an iframe should not have been enough to unwind a setting that enterprises were encouraged to treat as a serious control. The useful outcome is that OpenAI removed the dangerous permissions and the researchers waited to publish until after the fix.

This bug is separate from the October ChatGPT share-link sandbox escape reported by Parameter, which i10x also covers: two different preview-and-share problems, both now patched.

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 Check Point Research’s November write-up and The Hacker News’ November 2026 coverage. i10x did not reproduce the bypass.

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