# CVE-2025-48797: Gimp: multiple heap buffer overflows in tga parser

> Attackers can cause crashes or execute code by tricking users into opening specially crafted TGA image files in GIMP.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 May 2025
- **Updated:** 27 Jul 2026
- **Also known as:** CLSA-2025-1758744098, DEBIAN-CVE-2025-48797, GHSA-hrhw-58x6-vqj7

## What is CVE-2025-48797?

CVE-2025-48797 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 6, published on 27 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in GIMP when processing certain TGA image files. If a user opens one of these image files that has been specially crafted by an attacker, GIMP can be tricked into making serious memory errors, potentially leading to crashes and causing a heap buffer overflow.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

Apply the vendor's patch.

## Is CVE-2025-48797 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48797 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 6, published on 27 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-48797 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 6. 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-48797/ (Markdown: https://insights.sbomify.com/CVE-2025-48797/index.md)
```

## Sources

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

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