# CVE-2025-59820: Memory corruption in Krita

> Loading a manipulated TGA file in KDE Krita causes a heap-based buffer overflow, potentially allowing code execution or denial of service.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Nov 2025
- **Updated:** 6 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-59820, DLA-4395-1, DSA-6065-1, GHSA-r8j3-whr2-75m5, UBUNTU-CVE-2025-59820, openSUSE-SU-2025:15577-1

## What is CVE-2025-59820?

CVE-2025-59820 is a medium-severity memory corruption vulnerability in KDE Krita, published on 26 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2025-59820?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `krita` | openSUSE:Tumbleweed | All versions | 5.2.13-1.1 |

## How do I fix CVE-2025-59820?

Upgrade to a fixed version.

## Is CVE-2025-59820 being exploited?

There is no known exploitation of CVE-2025-59820 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59820 and fix it if it is affected.

What it is: CVE-2025-59820 is a medium-severity memory corruption vulnerability in KDE Krita, published on 26 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59820 in the wild and no public exploit code.

Affected product: KDE Krita. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59820/ (Markdown: https://insights.sbomify.com/CVE-2025-59820/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59820
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59820
- OSV: https://osv.dev/vulnerability/CVE-2025-59820

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59820/
Summaries are generated and may contain mistakes; the official description above is the record.