# CVE-2025-59801: Memory corruption in GhostXPS

> A stack-based buffer overflow in GhostXPS allows attackers to execute arbitrary code or cause denial of service via crafted TIFF data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:L/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:** 22 Sep 2025
- **Updated:** 23 Sep 2025
- **Also known as:** ALPINE-CVE-2025-59801, DEBIAN-CVE-2025-59801, ECHO-44a7-5b9c-a1d1, GHSA-h582-rvj3-8qw3, MINI-4g66-vjqg-27g8

## What is CVE-2025-59801?

CVE-2025-59801 is a medium-severity memory corruption vulnerability in Artifex GhostXPS, published on 22 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Artifex GhostXPS before 10.06.0, there is a stack-based buffer overflow in xps_unpredict_tiff in xpstiff.c because the samplesperpixel value is not checked.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

Upgrade to a fixed version.

## Is CVE-2025-59801 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59801 is a medium-severity memory corruption vulnerability in Artifex GhostXPS, published on 22 Sep 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-59801 in the wild and no public exploit code.

Affected product: Artifex GhostXPS. 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-59801/ (Markdown: https://insights.sbomify.com/CVE-2025-59801/index.md)
```

## Sources

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

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