Skip to main content
Menu
CVEs

Krita remote code execution in HEIC file parser

CVE-2026-134042Published , updated

7.8HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Summary

A flaw in how Krita parses HEIC files lets an attacker run arbitrary code on affected Krita installations. The attack is local and needs no login, but it requires a user to open a malicious file or visit a malicious page.

Written by a model

Original description

Krita HEIC File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Krita. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The issue results from the use of a vulnerable version of libheif. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28656.

Who should check

Anyone running Krita installations that parse HEIC files through a vulnerable libheif, including users who open files from untrusted sources.

“Krita HEIC File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability”

zerodayinitiative.com

What to do

  1. Check whether your setup matches what the bug needs.

    Krita is built or run with a vulnerable version of libheif
  2. Workaround: Restrict interaction with the product.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134042 (Krita HEIC File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134042 (entry last updated 2026-11-20):
Affected:
- Krita Krita: versions 5.2.15
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Krita is built or run with a vulnerable version of libheif (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1017/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
Workaround: Restrict interaction with the product. (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1017/)
CISA KEV: CVE-2026-134042 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134042 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.zerodayinitiative.com/advisories/ZDI-26-1017/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134042
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134042"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.8/10CVSS 7.8
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134042
RecordNVD · CVE-2026-134042
Other links 1
Linkzerodayinitiative.com · advisories/ZDI-26-1017

Questions about CVE-2026-134042

Is CVE-2026-134042 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The bug is an out-of-bounds write in Krita's HEIC file parsing. The advisory says a crafted file can lead to arbitrary code execution in the context of the current Krita process.

Source: zerodayinitiative.com

Which versions are affected by CVE-2026-134042?

Krita: version 5.2.15.

Source: cve.now feed data

Am I affected, and how do I check?

Krita builds or installations that use a vulnerable version of libheif are affected. To check, look at which libheif version the Krita build uses; the sources do not give a version range.

Source: zerodayinitiative.com

How do I fix CVE-2026-134042?

The sources name no fixed Krita version and no vendor patch IDs. The only mitigation they give is to restrict interaction with the product.

Source: zerodayinitiative.com

What if there's no patch?

Restrict interaction with the product, which is the only mitigation the advisory names. The sources give no other workaround.

Source: zerodayinitiative.com

Why do the sources disagree?

The description says remote attackers can trigger the bug, but the CVSS vector is AV:L, which means local access. Both statements appear in the sources and they do not match.

Source: zerodayinitiative.com

No corrections so far. Something wrong on this page? Report an error.