# CVE-2025-8534: libtiff tiff2ps tiff2ps.c PS_Lvl2page null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in libtiff's tiff2ps tool when specific options are enabled.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Aug 2025
- **Updated:** 5 Aug 2025
- **Also known as:** AZL-66078, AZL-66095, BELL-CVE-2025-8534, DEBIAN-CVE-2025-8534, ECHO-eac8-8550-89f3, GHSA-xgh3-993q-r2x8, JLSEC-2025-320, OESA-2025-2049, OESA-2025-2050, OESA-2025-2051, OESA-2025-2052, UBUNTU-CVE-2025-8534

## What is CVE-2025-8534?

CVE-2025-8534 is a low-severity vulnerability in Libtiff Libtiff, published on 4 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic was found in libtiff 4.6.0. This vulnerability affects the function PS_Lvl2page of the file tools/tiff2ps.c of the component tiff2ps. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 6ba36f159fd396ad11bf6b7874554197736ecc8b. It is recommended to apply a patch to fix this issue. One of the maintainers explains, that "[t]his error only occurs if DEFER_STRILE_LOAD (defer-strile-load:BOOL=ON) or TIFFOpen( .. "rD") option is used."

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Libtiff Libtiff.

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

Apply the vendor's patch.

## Is CVE-2025-8534 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8534 exists.

## Other vulnerabilities in Libtiff Libtiff

- [CVE-2004-1308](https://insights.sbomify.com/CVE-2004-1308/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0929](https://insights.sbomify.com/CVE-2004-0929/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-61144](https://insights.sbomify.com/CVE-2025-61144/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9533](https://insights.sbomify.com/CVE-2016-9533/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9534](https://insights.sbomify.com/CVE-2016-9534/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8534 is a low-severity vulnerability in Libtiff Libtiff, published on 4 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8534 exists.

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

## Sources

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

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