# CVE-2026-92413: Artifex MuPDF PDF Xref Loading pdf-stream.c pdf_open_filter null pointer dereference

> A remote attacker can cause a denial of service in MuPDF via a null pointer dereference in PDF stream loading, requiring a patch.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-pxvr-c538-2crq, UBUNTU-CVE-2026-92413

## What is CVE-2026-92413?

CVE-2026-92413 is a medium-severity vulnerability in Artifex MuPDF, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw has been found in Artifex MuPDF up to b6d17493700c621c0e70036980a6ebd06d2202c9. Affected by this vulnerability is the function pdf_open_filter of the file pdf-stream.c of the component PDF Xref Loading. Executing a manipulation can lead to null pointer dereference. The attack can be launched remotely. The exploit has been published and may be used. This patch is called 3df1e30f9d7b77260e13bd0dbe1928ddeba8386e. Applying a patch is advised to resolve this issue.

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

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


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

No fix has been published for CVE-2026-92413 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92413 is a medium-severity vulnerability in Artifex MuPDF, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92413 exists.

Affected product: Artifex MuPDF. 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-2026-92413/ (Markdown: https://insights.sbomify.com/CVE-2026-92413/index.md)
```

## Sources

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

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