Skip to content
Fencer Vulns
medium 6.7

CVE-2025-59820 json

In KDE Krita before 5.2.13, loading a manipulated TGA file could result in a heap-based buffer overflow in plugins/impex/tga/kis_tga_import…

published 2025-11-26 11 mo ago modified 2026-10-18 21 d ago also EUVD-2025-199710

cvss
6.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

In KDE Krita before 5.2.13, loading a manipulated TGA file could result in a heap-based buffer overflow in plugins/impex/tga/kis_tga_import.cpp (aka KisTgaImport). Control flow proceeds even when a number of pixels becomes negative.

Patch / fix

  • KDE Krita 5.2.13
  • krita Debian 12 1:5.1.5+dfsg-2+deb12u1
  • krita Debian 13 1:5.2.9+dfsg-1+deb13u1
  • krita Debian 14 1:5.2.13+dfsg-1

debian advisories DEBIAN-CVE-2025-59820

  • krita openSUSE Tumbleweed 5.2.13-1.1

opensuse advisories openSUSE-SU-2025:15577-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-59820 updated cvss 6.7

Krita: Krita: Heap-based buffer overflow via manipulated TGA file

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
11 mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.7 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

Affected products

  • KDE Krita

Classification

Weakness
  • CWE-1284 Improper Validation of Specified Quantity in Input

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.