Skip to content
Fencer Intel
critical 9.8

CVE-2019-9687 json

PoDoFo 0.9.6 has a heap-based buffer overflow in PdfString::ConvertUTF16toUTF8 in base/PdfString.cpp.

published 2019-03-11 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-19053

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

PoDoFo 0.9.6 has a heap-based buffer overflow in PdfString::ConvertUTF16toUTF8 in base/PdfString.cpp.

Patch / fix

  • libpodofo Debian 14, Debian 13, Debian 12 0.9.6+dfsg-5

debian advisories DEBIAN-CVE-2019-9687

  • podofo-0_10 openSUSE Tumbleweed 0.10.5-1.1
  • podofo openSUSE Tumbleweed 0.9.7-2.2

opensuse advisories openSUSE-SU-2025:15521-1openSUSE-SU-2024:11178-1

  • podofo Alpine 3.24, Alpine 3.23, Alpine 3.22 +9 more 0.9.7-r0

alpine advisories ALPINE-CVE-2019-9687

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • podofo Arch Linux 0.9.7-1

arch linux advisories AVG-867

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-2019-9687 updated cvss 3.3

podofo: heap-based buffer overflow in function PdfString::ConvertUTF16toUTF8 in base/PdfString.cpp

  • 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

2.20% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel 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.