OSV-2018-255
Heap-use-after-free in add_range
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5492
Crash type: Heap-use-after-free READ 4
Crash state:
add_range
pdf_map_range_to_range
pdf_parse_bf_range
What each source reports
OSV No score
Heap-use-after-free in add_range
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5492
Crash type: Heap-use-after-free READ 4
Crash state:
add_range
pdf_map_range_to_range
pdf_parse_bf_range
- Record
OSV-2018-255- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
mupdfOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2018-255 is a vulnerability with no CVSS score yet in mupdf, published January 15, 2021. No source lists public exploit code. A source reports a fix.