News

Wordfence Argus discovers critical libheif vulnerability affecting iPhone photo processing on servers

Wordfence Argus identifies a CVSS 9.8 flaw in libheif, used to process HEIC images. Code execution demonstrated on a live WordPress deployment.

UptimeMag editorial team · 18 September 2026 · 1 min read

Wordfence Argus scopre vulnerabilità critica in libheif, la libreria che apre le foto iPhone sui server

The Wordfence Argus team disclosed a critical vulnerability in libheif on Friday, 18 September 2026—the open-source library used by many servers to decode HEIC-format images, the standard format in which iPhones save photos. The flaw carries a CVSS score of 9.8, at the top of the severity scale. This affects anyone managing hosting and WordPress installations that accept image uploads: if the server processes HEIC images to generate thumbnails or conversions, libheif is often in the processing chain, even without the administrator's explicit knowledge.

What the Wordfence lab demonstrated

According to the official Wordfence post, the team demonstrated two concrete impacts on a specific WordPress deployment:

  • disclosure of protected files—the ability to read server contents that should remain confidential;
  • code execution on the target system.

Wordfence specifies that exploitation is "target-specific": the exploit demonstrated works on a precise configuration and is not a generic, ready-to-use attack against any server. The research, nicknamed internally "HEIF Heist", nonetheless demonstrates that adapting an image-based exploit to real-world systems is a practical operation, not merely theoretical.

What's missing to take action

The original announcement does not include, in the available text, the assigned CVE number or the exact versions of libheif that are vulnerable and patched. Before treating this information as operationally actionable for patching, server administrators should:

  1. Check the official Wordfence post (link below) for the associated CVE and libheif's changelog for affected versions;
  2. Verify whether your stack (hosting control panel, WordPress media plugins, image conversion tools) includes libheif as a dependency, direct or transitive;
  3. apply the update as soon as it becomes available from the project's official repository.

Source: Wordfence, official blog, 18 September 2026 — https://www.wordfence.com/blog/2026/09/wordfence-argus-discovers-critical-vulnerability-in-libheif-the-library-that-opens-iphone-photos-on-your-server/

Written with the help of artificial intelligence and checked by the editors (EU AI Act, art. 50). Source: Wordfence – vulnerabilità WordPress.