Skip to content
Fencer Vulns
medium 5.5

CVE-2020-19609 json

Artifex MuPDF before 1.18.0 has a heap based buffer over-write in tiff_expand_colormap() function when parsing TIFF files allowing attacker…

published 2021-07-21 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-11513

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

Artifex MuPDF before 1.18.0 has a heap based buffer over-write in tiff_expand_colormap() function when parsing TIFF files allowing attackers to cause a denial of service.

Patch / fix

  • artifex mupdf 1.18.0
  • mupdf Debian 14, Debian 13, Debian 12 1.17.0+ds1-2

debian advisories DEBIAN-CVE-2020-19609

  • mupdf Package Hub 15 SP3, Package Hub 15 SP2, Package Hub 15 SP1 +2 more 1.12.0-bp153.2.3.1

opensuse advisories openSUSE-SU-2021:1341-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-19609 updated cvss 5.5

mupdf: heap-based buffer overflow in tiff_expand_colormap() when parsing TIFF files

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.05% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • bugs.ghostscript.com https://bugs.ghostscript.com/show_bug.cgi?id=703076 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.