HEIF Heist: image parser RCE exploit
By exploiting underlying native libraries, these vulnerabilities allow an attacker to bypass application-level defenses and trigger memory corruption, data exposure, or remote code execution (RCE).The vulnerable attack surface lives below the application layer inside native C/C++ decoders such as libheif and libde265. After discovering and reporting a libheif RCE in Discourse, we asked a larger question: how many other applications depend on the same image-processing stack?Past vulnerabilities such as ImageTragick, ForcedEntry, and the libwebp flaw have demonstrated the reach of an image processor or parser vulnerability. Any backend processing untrusted user image uploads is potentially exposed to these parsers.What versions are affected, and how do I fix it?HEIF Heist is not tied to a single version.
- ▪By exploiting underlying native libraries, these vulnerabilities allow an attacker to bypass application-level defenses and trigger memory corruption, data exposure, or remote code execution (RCE).The vulnerable attack surface lives below t
- ▪After discovering and reporting a libheif RCE in Discourse, we asked a larger question: how many other applications depend on the same image-processing stack?Past vulnerabilities such as ImageTragick, ForcedEntry, and the libwebp flaw have
- ▪Any backend processing untrusted user image uploads is potentially exposed to these parsers.What versions are affected, and how do I fix it?HEIF Heist is not tied to a single version.
Hacker News (Front Page) files mainly under programming. We currently carry 1,823 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacktron |
| Canonical URL | https://heif-heist.com |
| Publication time | Fri, 18 Sep 2026 13:39:29 +0000 |
| Retrieval time | 2026-09-18T16:08:45.274Z |
| Last seen | 2026-09-18T16:08:45.274Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | -3FEscRgPmlZ · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
HEIF HeistOne image parser to pwn them all01 Overview02 Research origin03 FAQWhat is HEIF Heist?A bug that could have allowed us toDump of OpenAI private repositoriesRCE on Slack which allows leaking filesRCE in Meta's core product suite via image uploadLeak arbitrary Redacted users' tokens, and AWS access tokensAuthenticated RCE on DiscourseUnauthenticated RCE in Next.js via AVIF Image OptimizationAuthenticated RCE on GitHub Enterprise (CVE-2026-19118)RCE on multiple web frameworks/cms.Leak user's files, and sensitive info from multiple applications.HEIF Heist is Hacktron's name for a class of remote attack paths targeting services that decode attacker-controlled HEIF, HEIC, or AVIF images.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacktron.
Discussion
0 commentsMore from Hacktron
