VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libpodofo: vulnerability history, versions and safety

libpodofo is a package in the Debian ecosystem. Vulert records 107 vulnerabilities for it across 8 releases, from Mar 2017 to Oct 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
107 vulnerabilities recorded U107
i
21 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libpodofo vulnerabilities

Vulert verdict on libpodofo i

Updated on 23 Oct 2026

Careful: 21 of the 107 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 107 vulnerabilities on record across 8 years, none in the last year.

What to do: Plan around the 21 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 107 over 8 years · 0 in the last year i
  • Latest disclosure 01 Oct 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 21 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for libpodofo, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 8 of 8 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 54
  • 2018 28
  • 2019 10
  • 2021 9
  • 2023 4
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 107 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for libpodofo

The 5 most severe of 107 vulnerabilities recorded for this package

Search all 107 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-Based Buffer Overflow in PoDoFo's PdfParser - CVE-2015-8981 9.8 critical 0.9.4-1 16 Mar 2017
Heap-Based Buffer Overflow in PoDoFo 0.9.6 - libpodofo Package Vulnerability 9.8 critical 0.9.6+dfsg-5 11 Mar 2019
Heap-Based Buffer Overflow in PoDoFo Library (CVE-2017-8378) 9.8 critical 0.9.5-9 01 May 2017
Heap Use-After-Free Vulnerability in libpodofo - CVE-2023-31566 8.8 high No fix published 10 May 2023
Heap Buffer Overflow in PoDoFo Package: CVE-2023-31567 8.8 high No fix published 10 May 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libpodofo

Is libpodofo safe to use?

Vulert records 107 vulnerabilities for libpodofo in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 107 not yet rated. 21 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libpodofo have?

107 vulnerabilities are recorded for libpodofo in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 107 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libpodofo vulnerabilities disclosed?

0 vulnerabilities were recorded for libpodofo in the last 12 months, and the oldest entry in this database dates to 01 Mar 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of libpodofo are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor libpodofo for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libpodofo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.