# Pillow: Memory disclosure and segfault in libtiff encoder via crafted TIFF tags

Advisory record · `GHSA-xvh5-g6gv-559v`

- **Identifiers:** `GHSA-xvh5-g6gv-559v` · `CVE-2026-112902`
- **State:** Confirmed
- **Severity:** CVSS 8.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-686](https://cwe.mitre.org/data/definitions/686.html)
- **Tags:** [CWE-686](https://agentprime.io/advisories/tag/cwe-686.md)
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Oct 2026, 21:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pillow` (PyPI): affected `<13.0.0`; fixed in `13.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Pillow versions before 13.0.0 are vulnerable. A crafted TIFF of a few hundred bytes can make Pillow's libtiff encoder copy process memory into a re-saved TIFF or crash the process. An attacker who can get the application to open and re-save such a file, with compressed TIFF output, can read memory or cause a crash. Upgrade to Pillow 13.0.0 or later. The source gives no other workaround.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.3 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xvh5-g6gv-559v)
- 5 Nov 2026, 20:38 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-112902)
- 5 Nov 2026, 21:18 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-112902)

## Sources

- [GitHub Advisory Database: GHSA-xvh5-g6gv-559v](https://github.com/advisories/GHSA-xvh5-g6gv-559v)
- [OSV: GHSA-xvh5-g6gv-559v](https://osv.dev/vulnerability/GHSA-xvh5-g6gv-559v)
- <https://github.com/python-pillow/Pillow/security/advisories/GHSA-xvh5-g6gv-559v>
- <https://github.com/python-pillow/Pillow/commit/af56ace297b0991d02988fcc2ea933e4824b4fb3>
- <https://github.com/python-pillow/Pillow>
- <https://github.com/python-pillow/Pillow/releases/tag/13.0.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xvh5-g6gv-559v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xvh5-g6gv-559v/>. Everything for agents: <https://agentprime.io/llms.txt>.