# CVE-2026-7233: Artifex MuPDF CFF Index subset-cff.c fz_subset_cff_for_gids out-of-bounds

> A local attacker can trigger an out-of-bounds read in MuPDF's CFF Index Handler, potentially causing a crash or information disclosure.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2026
- **Updated:** 5 May 2026
- **Also known as:** DEBIAN-CVE-2026-7233, GHSA-82r2-3cm6-cxw2, UBUNTU-CVE-2026-7233

## What is CVE-2026-7233?

CVE-2026-7233 is a medium-severity memory corruption vulnerability in Artifex Mupdf, published on 28 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in Artifex MuPDF up to 1.28.0. The impacted element is the function fz_subset_cff_for_gids of the file subset-cff.c of the component CFF Index Handler. This manipulation causes out-of-bounds read. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through a bug report but has not responded yet.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Artifex Mupdf.

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

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

## Is CVE-2026-7233 being exploited?

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

## Other vulnerabilities in Artifex Mupdf

- [CVE-2019-7321](https://insights.sbomify.com/CVE-2019-7321/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-6525](https://insights.sbomify.com/CVE-2016-6525/): Memory corruption in n/a (critical 9.8)
- [CVE-2011-0341](https://insights.sbomify.com/CVE-2011-0341/): Memory corruption in n/a (critical 9.3)
- [CVE-2016-8728](https://insights.sbomify.com/CVE-2016-8728/): Memory corruption in MuPDF (high 8.6)
- [CVE-2021-3407](https://insights.sbomify.com/CVE-2021-3407/): Use after free in mupdf (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7233 is a medium-severity memory corruption vulnerability in Artifex Mupdf, published on 28 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7233 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-7233/ (Markdown: https://insights.sbomify.com/CVE-2026-7233/index.md)
```

## Sources

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

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