Xpdf vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited46 versions
The short answer

Xpdf is made by Xpdfreader. We track 82 published vulnerabilities in it, across 46 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 3 November 2021. If you run Xpdf, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Xpdf flaw added to the known-exploited list is CVE-2021-30860, on 3 November 2021. We keep watching the known-exploited list.

Versions

Which versions of Xpdf do the exploited flaws hit?

Each exploited flaw lists the versions it affects, usually as ranges. "before 4.04" means every version up to, but not including, 4.04. Find your version, then patch.

  • CVE-2021-30860Exploited list, 3 Nov 2021

    Apple Multiple Products Integer Overflow Vulnerability

    before 4.04
Known exploited

Which Xpdf vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.8
    CVE-2021-30860HighKnown exploited
    Apple Multiple Products Integer Overflow Vulnerability

    Apple iOS, iPadOS, macOS, and watchOS CoreGraphics contain an integer overflow vulnerability which may allow code execution when processing a maliciously crafted PDF.

    Chance of use76%Known exploited since3 Nov 2021
Exploit likelihood

Which Xpdf flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 2.9%

    The error function in Error.cc in poppler before 0.21.4 allows remote attackers to execute arbitrary commands via a PDF containing an escape sequence for a terminal emulator.

    CVSS7.8Published9 Jan 2020
  2. 2.1%

    Xpdf 4.02 allows stack consumption because of an incorrect subroutine reference in a Type 1C font charstring, related to the FoFiType1C::getOp() function.

    CVSS7.5Published26 Dec 2020
  3. 1.6%

    There is an invalid memory access in the TextLine class in TextOutputDev.cc in Xpdf 4.0.4 because the text extractor mishandles characters at large y coordinates.

    CVSS7.8Published9 May 2022
  4. 1.6%

    XRef::fetch in XRef.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (stack consumption) via a crafted pdf file, related to AcroForm::scanField, as demonstrated by pdftohtml.

    CVSS5.5Published3 Sep 2018
  5. 1.3%

    The DCTStream::readHuffSym function in Stream.cc in the DCT decoder in xpdf before 4.00 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted...

    CVSS7.8Published14 May 2018
  6. 1.2%

    CCITTFaxStream::readRow() in Stream.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted pdf file, as demonstrated by pdftoppm.

    CVSS5.5Published18 Oct 2018
  7. 1.2%

    There is an invalid memory access in the function GfxIndexedColorSpace::mapColorToBase() located in GfxState.cc in Xpdf 4.0.0, as used in pdfalto 0.2.

    CVSS7.8Published21 Mar 2019
Precursor Intelligence

Running Xpdf? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 82 published vulnerabilities listed under the name Xpdf, across 46 versions. The most recent Xpdf flaw added to the known-exploited list is CVE-2021-30860, on 3 November 2021.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2021-30860.

Each flaw names its own versions, usually as ranges. The newest, CVE-2021-30860, affects before 4.04. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Xpdf. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.