# CVE-2026-120752: PyMuPDF 1.25.3 before 2.0 Stack Buffer Overflow via add_freetext_annot() Callout


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120752, GHSA-x2mr-6hpr-g257, UBUNTU-CVE-2026-120752, openSUSE-SU-2026:12554-1

## What is CVE-2026-120752?

CVE-2026-120752 is a high-severity vulnerability in PyMuPDF, published on 2 Nov 2026. 

### Official description

PyMuPDF 1.25.3 before 2.0 contains a stack-based buffer overflow vulnerability in JM_set_annot_callout_line() that copies a caller-supplied number of callout points into a fixed three-element stack array. Attackers who control the callout argument passed to Page.add_freetext_annot() can supply four or more points to overwrite the stack frame, crashing the process or executing code.

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

## Which versions are affected by CVE-2026-120752?

1 open source package ship an affected version, including pymupdf.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `pymupdf` | PyPI | `pkg:pypi/pymupdf` | From 1.25.3 | 2.0 |
| `python-PyMuPDF` | openSUSE:Tumbleweed | `pkg:rpm/opensuse/python-PyMuPDF` | All versions | 2.1-1.1 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| openSUSE | Tumbleweed | fixed | `python-PyMuPDF` | 2.1-1.1 |

## How do I fix CVE-2026-120752?

Upgrade pymupdf to 2.0 or later.

## Is CVE-2026-120752 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120752 and fix it if it is affected.

What it is: CVE-2026-120752 is a high-severity vulnerability in PyMuPDF, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120752 exists.

Affected packages and fixed versions:
- pymupdf (PyPI): affected from 1.25.3; fixed in 2.0

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-2026-120752/ (Markdown: https://insights.sbomify.com/CVE-2026-120752/index.md)
```

## Sources

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

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