Zero-Day Vulnerability in Krita Allows Remote Code Execution via HEIC File Parsing
A critical remote code execution vulnerability (ZDI-26-1017) has been disclosed in the popular open-source painting application Krita, stemming from a flaw in its HEIC file parsing component.

A critical vulnerability, designated ZDI-26-1017, has been publicly disclosed in Krita, a widely-used open-source digital painting application. The flaw resides within the application's handling of HEIC image files, specifically an out-of-bounds write condition that can be triggered by specially crafted files.
Successful exploitation of this vulnerability requires user interaction. Attackers can trick victims into opening a malicious HEIC file or visiting a compromised webpage that serves such a file. Upon successful exploitation, an attacker could achieve arbitrary code execution on the affected system, operating within the privileges of the current Krita process. The vulnerability has been assigned a CVSS score of 7.8, indicating a high severity.
The root cause of the vulnerability is attributed to the use of a vulnerable version of the libheif library, which Krita relies on for processing HEIC images. This library component contains the exploitable out-of-bounds write flaw. When Krita attempts to parse a malformed HEIC file, it can lead to memory corruption, allowing an attacker to overwrite critical data structures and gain control of the program's execution flow.
The Zero Day Initiative (ZDI) reported the vulnerability to the vendor on December 24, 2025. After acknowledging the report, a lengthy disclosure process ensued, with ZDI following up multiple times. Ultimately, with no patch available and the vendor not responding to requests for an update, ZDI proceeded with a public disclosure on November 18, 2026, classifying it as a zero-day advisory due to the lack of a vendor fix at the time of publication.
Given the nature of the vulnerability, which requires user interaction through opening a malicious file or visiting a compromised site, the primary mitigation strategy recommended by ZDI is to restrict user interaction with untrusted HEIC files or sources. Users should exercise caution when opening files from unknown or untrusted origins. As of the advisory's publication, no patch has been released by the Krita developers.
This vulnerability highlights the ongoing risks associated with parsing complex file formats, even in open-source applications. Software that handles user-provided or externally sourced files, such as image parsers, remains a prime target for attackers seeking to achieve remote code execution. The reliance on third-party libraries, like libheif, also introduces supply chain risks, as vulnerabilities in these components can cascade into multiple applications.
While Krita is a powerful tool for artists, its widespread use means that a successful exploit could impact a significant number of users. The disclosure as a zero-day underscores the importance of prompt vendor response to security advisories and the challenges faced by security researchers in ensuring vulnerable software is patched before exploitation becomes widespread.
Users are advised to stay informed about potential patches or updates from the Krita project and to implement cautious file handling practices until a permanent solution is available. The vulnerability, ZDI-26-1017, serves as a reminder of the persistent threats posed by memory corruption vulnerabilities in widely used software.
This advisory details a new critical vulnerability, ZDI-26-1016, affecting Krita's EXR file parsing component. Unlike the previously reported PSB file parsing flaw (ZDI-26-1013), this vulnerability is an integer overflow that can lead to remote code execution when a user opens a malicious EXR file or visits a compromised webpage.
This advisory details a heap-based buffer overflow vulnerability in Krita's HEIC file parsing, distinct from the previously reported ZDI-26-1017 which focused on a different HEIC parsing flaw. The vulnerability, identified as ZDI-26-1015, stems from an outdated version of the libde265 library and allows for remote code execution within the context of the current process. While user interaction is required, the potential for arbitrary code execution makes this a significant finding.