Raw SignalSep 18, 20261 min read1 source

Hacktron chains libheif and SSO flaws to access OpenAI employee accounts

Hacktron described chaining a libheif heap overflow on OpenAI's Discourse forum with an SSO flaw to take over OpenAI employee ChatGPT accounts, using Claude models.

In one minute

Hacktron described chaining a libheif heap overflow on OpenAI's Discourse forum with an SSO flaw to take over OpenAI employee ChatGPT accounts, using Claude models. Hacktron reported that on July 25, 2026 it chained two critical vulnerabilities to take over multiple OpenAI employees' ChatGPT accounts and open a proof-of-concept pull request in an internal OpenAI repository. The chain began with

Hacktron reported that on July 25, 2026 it chained two critical vulnerabilities to take over multiple OpenAI employees' ChatGPT accounts and open a proof-of-concept pull request in an internal OpenAI repository. The chain began with a libheif heap buffer overflow in OpenAI's Discourse forum, found and exploited using Claude Opus 4.8 and Opus 5. OpenAI fixed its side within about 14 hours and paid a $6,500 bounty.

The root cause is a supply-chain gap: an upstream fix was not labelled as security-relevant, so Debian 12 images shipped vulnerable libheif 1.19.7. Services processing user-supplied HEIC or HEIF images should check libheif. The excerpt does not detail the SSO flaw itself.

Evidence / sources

  1. 1hacktron.ai/blog/hacking-openai
All Raw Signals

Next reads

Read next

Open the graph
  1. 01topicSecurityExplore the security topic hub.
  2. 02topicAi Assisted SecurityExplore the ai-assisted-security topic hub.
  3. 03archiveRaw SignalsOpen every source-linked raw signal.
  4. 04source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract