How severe is GHSA-cxqh-p2w9-fmr7?

No CVSS score has been assigned to GHSA-cxqh-p2w9-fmr7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cxqh-p2w9-fmr7?

GHSA-cxqh-p2w9-fmr7 affects the following packages: pymupdf (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-cxqh-p2w9-fmr7?

Update pymupdf to 1.26.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cxqh-p2w9-fmr7 is resolved across your whole dependency graph.

How do I detect GHSA-cxqh-p2w9-fmr7 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pymupdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cxqh-p2w9-fmr7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-cxqh-p2w9-fmr7?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cxqh-p2w9-fmr7 can be triaged on real exposure rather than presence alone.

Is GHSA-cxqh-p2w9-fmr7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cxqh-p2w9-fmr7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cxqh-p2w9-fmr7?

GHSA-cxqh-p2w9-fmr7 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cxqh-p2w9-fmr7?

GHSA-cxqh-p2w9-fmr7 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-cxqh-p2w9-fmr7 published, and has it been updated?

GHSA-cxqh-p2w9-fmr7 was published on March 19, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-cxqh-p2w9-fmr7 — pymupdf

Fix: pymupdf/PyMuPDF@603cafe

GHSA-cxqh-p2w9-fmr7 is a Path Traversal vulnerability in pymupdf. A fix is available for pymupdf — see the affected versions and patch details below.

PyMuPDF has a path traversal in _main_.py

Also known asCVE-2026-3029PYSEC-2026-3001

Published

Mar 19, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cxqh-p2w9-fmr7.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍pymupdf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

A path traversal and arbitrary file write vulnerability exist in the embedded get function in 'main.py' in PyMuPDF version, 1.26.5.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pymupdf`	≥ 1.26.5&&< 1.26.7	1.26.7`pip install --upgrade 'pymupdf==1.26.7'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pymupdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pymupdf to 1.26.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cxqh-p2w9-fmr7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cxqh-p2w9-fmr7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cxqh-p2w9-fmr7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A path traversal and arbitrary file write vulnerability exist in the embedded get function in '_main_.py' in PyMuPDF version, 1.26.5.

O3 Security · Impact-Aware SCA

Is GHSA-cxqh-p2w9-fmr7 in your dependencies?

O3 Security finds GHSA-cxqh-p2w9-fmr7 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works