AIToday
Large Language ModelsAI Safety & AlignmentZenn AI/MLPublished: Oct 1, 2026, 10:00 JST

Hacktron used Claude to breach OpenAI in under 72 hours

Hacktron used Claude to breach OpenAI in under 72 hours

3 Key Points

  1. What happened

    Three Hacktron researchers entered through an image upload on OpenAI's help forum, exploiting an unpatched libheif fix with no CVE and a misconfigured SSO, then used Claude Opus 4.8 and Opus 5 to build the exploit in under 72 hours.

  2. Why it matters

    The report calls this turning scarce expertise into compute, meaning attackers no longer need specialist teams, long timelines, or prior knowledge of the target setup, which broadens who is worth attacking.

  3. What to watch

    The underlying causes were ordinary — a fix that never reached Debian packages and an SSO misconfiguration — so defense hinges on shrinking exposed features and limiting blast radius. Watch the GHSA-vhm9-85gw-x335 advisory.

WHO IT HITSSecurity and platform engineers who run web services and internal tools — especially those deciding when to update dependency libraries — are the ones who may need to revisit which file formats they accept, sandbox untrusted parsing, and audit shared log-ins across forums, wikis, and admin panels.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The report, published in September 2026 by three researchers at security firm Hacktron, was drawn from work done inside OpenAI's bug bounty program. It describes a path that started with an image upload on OpenAI's help forum and ended with access to employee ChatGPT and Codex accounts, plus one harmless pull request against an internal repository.

The two root causes are mundane. An image-processing library called libheif had a security fix that carried no CVE and was never pulled into Debian's packages, and OpenAI's SSO was misconfigured. Neither problem came from AI. What the researchers passed to AI was the exploit work itself: starting without exact knowledge of the target library version, libc version, or deployment environment, they adapted an ARM64 exploit that ran in about three hours with Opus 5, after repeated stumbles on hardened environments with Opus 4.8.

The authors frame this as AI converting scarce expertise into compute — pay, and you can get something like a specialist. The practical reading is that defenses built on attackers' effort rather than on design are weakening, and the outcome for any given organization likely hinges on whether it has quietly exposed features it does not use and blurry trust boundaries between its core service and peripheral tools.

FAQ
How did the attackers get in?
Through an image upload on OpenAI's help forum, which was built on Discourse. The root causes were a libheif security fix that had no CVE and was not pulled into Debian packages, and a misconfiguration in OpenAI's SSO.
What did OpenAI do?
OpenAI fixed the issue about 14 hours after the report and paid a $6,500 bounty. Discourse published an advisory, GHSA-vhm9-85gw-x335, and added ImageMagick sandboxing alongside the fix.
Does running apt upgrade protect against this?
Not necessarily. Because the libheif fix carried no CVE, it was not included in distribution security updates, so a vulnerable version stayed even when apt upgrade was run properly.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGoogle unveils Gemini 4 Argon, limits early access