Cybersecurity Research

Researchers Chain Forum Image Bug and Login Flaw to Reach OpenAI's Internal Code

Hacktron · 13 Sept 2026
Key Takeaway If your applications accept user-uploaded images, check which image libraries they rely on and patch them promptly, because a single dependency can open a path into your wider systems.

Security firm Hacktron says it chained two critical vulnerabilities on 25 July 2026 to compromise several OpenAI employees' ChatGPT accounts. From those accounts, the team could reach internal OpenAI repositories and potentially many connected services. To prove access without viewing sensitive data, they used an employee's Codex account to open a harmless pull request in OpenAI's internal monorepo, then stopped testing.

The first step was remote code execution on OpenAI's help forum at community.openai.com, which runs on Discourse. Researchers found that Discourse passes HEIC and HEIF images to ImageMagick for conversion, which exposes the libheif parser to attacker-controlled files. The Discourse Docker image, based on Debian 12, shipped libheif 1.19.7, which lacked security fixes that were never back-ported. The upstream change was not labelled a security fix and received no CVE, which may explain the delay. Hacktron says Debian 13 still shipped vulnerable version 1.19.8, with an update published on 8 August 2026.

The second step was an SSO misconfiguration in OpenAI's identity setup. The forum offers "Sign in with OpenAI" through auth.openai.com, so control of the forum created a path into broader accounts. Because ChatGPT and Codex can connect to services such as GitHub, Slack and email, the potential reach was large. Hacktron says the whole process took under 72 hours from finding the bug to reaching internal repositories.

OpenAI confirmed its fix about 14 hours after the report, and Discourse had a patch two days after being notified, adding image-processing sandboxing as extra protection. OpenAI paid a $6,500 bounty but said testing against the Discourse-hosted forum was excluded from its programme, and the award covered only the OpenAI-side finding. Hacktron warns that many applications accepting .heic, .heif or .avif uploads may be affected by the same library.

Why it matters

The failure was not in the main application but in an unlabelled upstream fix that Linux distributions missed, so scanners keyed to CVEs would not have flagged it. It also breaks the assumption that a low-value forum is isolated: shared single sign-on turned it into a route to accounts with connected tools like GitHub, Slack and email. Any business that uses one identity provider across public-facing and internal services must treat its weakest connected app as part of the core.

What to do

  • Rebuild self-hosted Discourse now by running git pull then ./launcher rebuild app from /var/discourse, as a web update alone may not replace the image.
  • Review the Discourse security advisory GHSA-vhm9-85gw-x335 for patch and rebuild guidance.
  • Identify applications that accept .heic, .heif or .avif uploads and update libheif and ImageMagick in them.
  • Review which services your single sign-on exposes to public-facing apps such as forums.
Answering to more than one framework? Run them as one security and AI governance programme ->

Summarised by CISO AI from Hacktron, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.