AINewsIQ by Triuna Labs
Menu
SOURCE-LINKED SIGNAL / ARTICLE / SECURITY

Exfiltrating Your ChatGPT Chat History and Memories With Prompt Injection

The author describes a bypass of OpenAI's url_safe rendering feature that allows ChatGPT to send personal information, including chat history, to a third-party server via prompt injection in untrusted content such as websites or PDFs.

READ THE ORIGINAL SOURCEOpen original sourceembracethered.com UTC

Source-based brief · Editor review not recorded · See checks and limits ↓

⚑ Recency not confirmed · what to check

We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news.

Claim context: the full exploit payload was not published and the fix status rests on the author's update.

Recorded links

One primary source; other links are context, not independent corroboration.

Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.

Open full article view →
How this score was derived
  • Linked article+30
  • Fetched source page+30
  • No editor link review+0
  • Original non-discussion link+5
  • Recency not confirmed-8

This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.

View full scoring →Read the scoring rubric →

What the source says

The author describes a bypass of OpenAI's url_safe rendering feature that allows ChatGPT to send personal information, including chat history, to a third-party server via prompt injection in untrusted content such as websites or PDFs. The author reports using an Azure Blob Storage domain that is considered url_safe as the exfiltration channel. The post says the issues were reported to OpenAI in October 2024, that the root cause was reported over two years earlier, and that the vulnerability was addressed by OpenAI on August 26, 2025. The author withheld the full prompt injection payload.

Claim explorer

Attribution, source and conditions

Source-stated points from the stored brief. Claim-level assessments have not been recorded.

The author reports that url_safe bypasses reported in October 2024 remained unfixed when the research was…
Source assertionNot independently checked
Primary sourceembracethered.comInspect source ↗
Attributed toClaimant not recorded per pointSource assertion
Conditions / limitsClaim-specific conditions not recorded. Read the source and limits below.

Source claims not independently checked; the full exploit payload was not published and the fix status rests on the author's update.

This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.

Questions worth asking

Open questions for further reporting
What remains unconfirmed?

Source claims not independently checked; the full exploit payload was not published and the fix status rests on the author's update.

What material was available for this brief?

The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.

Limits from the stored brief

Source claims not independently checked; the full exploit payload was not published and the fix status rests on the author's update.

This is a source-based abstract, not independent validation of the source's claims.

Join the discussion

Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.

No published comments yet.

Checking sign-in…

New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →