HEIF Heist Image Parser Flaws Tied to RCE
Hacktron's HEIF Heist links libheif and libde265 flaws to image-upload RCE affecting Slack, Meta, GitHub, Discourse, and OpenAI.
Hacktron's HEIF Heist research describes memory-unsafe HEIF and AVIF parsing in libheif and libde265, reached through ImageMagick, libvips, and Sharp, that can lead to heap disclosure and remote code execution from crafted image uploads. The reports cite affected paths in Slack, Meta products, Discourse, Next.js, and GitHub Enterprise Server, including authenticated RCE tracked as CVE-2026-19118. In July 2026, researchers chained a libheif heap-buffer overflow in Discourse with an OpenAI SSO flaw and received a $6,500 bounty; one source says OpenAI patched within 14 hours. Sources disagree on what that chain exposed: employee ChatGPT accounts in one account, an employee's Codex account and an internal GitHub repository in another, and internal repositories more generally in a third. They also disagree on the AI used, naming Claude Opus 5, Anthropic's Claude, or unnamed agentic workflows that cut exploit development to one to three days. No active malware campaigns were identified, and suggested mitigations include patching the libraries, restricting formats in ImageMagick policy, and sandboxing conversion.
- Hacktron's HEIF Heist research describes memory-unsafe libheif and libde265 parsers for HEIC, HEIF, and AVIF, reached via ImageMagick, libvips, and Sharp.
- Reported effects include heap disclosure and remote code execution from crafted image uploads, with paths cited in Slack, Meta products, Discourse, Next.js, and GitHub Enterprise Server.
- CVE-2026-19118 is described as authenticated remote code execution in GitHub Enterprise Server.
- In July 2026, a libheif heap-buffer overflow in Discourse was chained with an OpenAI SSO flaw; OpenAI paid a $6,500 bounty and, per one report, patched within 14 hours.
- Sources disagree on the OpenAI outcome: employee ChatGPT accounts versus an employee's Codex account and an internal GitHub repository, with a third report citing internal repositories more generally.
- Sources also disagree on AI assistance, naming Claude Opus 5, Anthropic's Claude, or unspecified agentic workflows that shortened development to one to three days.
- One report said no active malware campaigns had been identified.
- Cited mitigations are patching libheif and libde265, restricting formats in ImageMagick policy, and sandboxing conversion.
Coverage timelineoldest first · each row is one article
- · 5d agoHEIF Heist Image Flaws Let Attackers Gain RCE Across Meta, Slack and GitHub Enterprise
GBHackers· 78
Hacktron's "HEIF Heist" research shows memory-unsafe HEIF/AVIF parsers enable RCE and data leaks in Slack, Meta, GitHub Enterprise, and OpenAI.
- · 5d agoClaude Opus 5 Helps Researchers Weaponize HEIF Image Flaw Into Remote Code Execution
Cyber Security News· 72
Researchers used Claude Opus 5 to help weaponize a HEIF image processing flaw into a remote code execution exploit.
- · 4d agoResearchers used Claude to hack OpenAI
Malwarebytes Labs· 75
Vulnerabilities in this storyAll →
- CVE-2026-191187.7<1%Race Condition RCE in GitHub Enterprise Serverpublished · github enterprise server
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-19118 | Race Condition RCE in GitHub Enterprise Server CVE-2026-19118 is a time-of-check time-of-use (TOCTOU) race condition (CWE-367) in GitHub Enterprise Server that can lead to remote code execution. An attacker needs an authenticated account with write access to a repository and must time concurrent upload requests precisely to win the race window. If triggered successfully, the attacker gains remote code execution on the GHES appliance, taking control of the self-hosted instance and the code repositories it hosts. All versions of GitHub Enterprise Server prior to 3.22 are affected, and fixes are available in the 3.17.20, 3.18.14, 3.19.11, 3.20.7, and 3.21.5 maintenance releases. There is no public proof-of-concept, the flaw is not in CISA KEV, and EPSS estimates only a 0.5% probability of exploitation within 30 days, so no exploitation is currently known. |