CVE-2025-55780
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA null pointer dereference occurs in the function break_word_for_overflow_wrap() in MuPDF 1.26.4 when rendering a malformed EPUB document. Specifically, the function calls fz_html_split_flow() to split a FLOW_WORD node, but does not check if node->next is valid before accessing node->next->overflow_wrap, resulting in a crash if the split fails or returns a partial node chain.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA null pointer dereference vulnerability exists in MuPDF 1.26.4 within the break_word_for_overflow_wrap() function when rendering EPUB documents. The function calls fz_html_split_flow() to split a FLOW_WORD node but fails to validate that node->next exists before accessing node->next->overflow_wrap, causing a crash when the split operation fails or returns an incomplete node chain.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.24.0, < 1.26.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed MuPDF versionRun 'mupdf --version' from command line, or check the shared library file version (libmupdf.so on Linux systems, mupdf.dll on Windows). On Linux also try: dpkg -l | grep mupdf or rpm -qa | grep mupdfAffected if Version is 1.24.0, 1.24.1, 1.24.2, 1.24.3, 1.24.4, 1.24.5, 1.25.0 through 1.25.x, 1.26.0 through 1.26.6, or any version >= 1.24.0 and < 1.26.7
-
Identify if EPUB processing is enabledInspect the application or tool using MuPDF to confirm it supports EPUB format. Check configuration files, plugins, or document type associations for .epub file handling. Look for EPUB-specific modules or the fz_html_split_flow function in any custom integrationAffected if The tool is configured to render or parse EPUB documents using MuPDF's HTML/EPUB rendering engine
-
Verify the vulnerable code path can be triggeredAttempt to process a malformed or specially crafted EPUB file that triggers the overflow wrap code path in break_word_for_overflow_wrap(). Monitor for crashes or null pointer errors during EPUB rendering, particularly when text overflow handling occursAffected if Processing EPUB documents causes the application to call break_word_for_overflow_wrap() on an incomplete node chain from fz_html_split_flow()
Environment is affected if MuPDF version is 1.24.0 or higher but below 1.26.7 AND the software uses MuPDF to render EPUB documents, enabling the vulnerable break_word_for_overflow_wrap() function to be invoked.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.26.7
Update MuPDF to the latest patched version. Until an update is available, avoid processing untrusted or malformed EPUB documents with vulnerable versions.
MuPDF 1.26.7 or later
- Identify all systems and applications using MuPDF versions 1.24.0 through 1.26.6
- Upgrade MuPDF to version 1.26.7 or later (the latest stable 1.26.x release recommended)
- Verify the upgrade by checking the MuPDF library version
- Test EPUB document rendering to confirm the fix resolves the null pointer dereference
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55780 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data