Glyphandcog maintains a focused portfolio of PDF processing utilities—including Xpdf, Xpdfreader, and pdftops—that are embedded across numerous document-handling workflows and command-line environments despite their narrow vendor footprint. The vulnerability landscape for this vendor is shaped by the structural complexity of PDF parsing: recurring weaknesses center on memory-safety issues such as out-of-bounds reads, buffer-boundary violations, integer overflows, and NULL-pointer dereferences, along with improper input validation against malformed or adversarial PDF structures. These weakness classes are characteristic of C-based parsers operating on untrusted binary formats, where a single crafted document can trigger memory corruption or denial-of-service conditions. Defenders relying on these utilities should monitor for updates and treat PDF processing as a potential attack vector, particularly in automated or network-exposed contexts. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Glyphandcog over time
Signals from CVEs in this vendor scope (56 CVEs).
56 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2009-3603HIGH Integer overflow in the SplashBitmap::SplashBitmap function in Xpdf 3.x before 3.02pl4 and Poppler before 0.12.1 might allow remote attackers to execute arbitrary code via a crafte | Oct 21, 2009 | 9.3 | 33 | NO | NO |
CVE-2009-3608HIGH Integer overflow in the ObjectStream::ObjectStream function in XRef.cc in Xpdf 3.x before 3.02pl4 and Poppler before 0.12.1, as used in GPdf, kdegraphics KPDF, CUPS pdftops, and te | Oct 21, 2009 | 9.3 | 32 | NO | NO |
CVE-2009-3604HIGH The Splash::drawImage function in Splash.cc in Xpdf 2.x and 3.x before 3.02pl4, and Poppler 0.x, as used in GPdf and kdegraphics KPDF, does not properly allocate memory, which allo | Oct 21, 2009 | 9.3 | 32 | NO | NO |
CVE-2009-3606HIGH Integer overflow in the PSOutputDev::doImageL1Sep function in Xpdf before 3.02pl4, and Poppler 0.x, as used in kdegraphics KPDF, might allow remote attackers to execute arbitrary c | Oct 21, 2009 | 9.3 | 31 | NO | NO |
CVE-2011-0764MEDIUM t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6, teTeX, and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attacke | Mar 31, 2011 | 6.8 | 27 | NO | NO |
CVE-2021-40226HIGH xpdfreader 4.03 is vulnerable to Buffer Overflow. | Nov 10, 2022 | 7.5 | 25 | NO | NO |
CVE-2022-24106HIGH In Xpdf prior to 4.04, the DCT (JPEG) decoder was incorrectly allowing the 'interleaved' flag to be changed after the first scan of the image, leading to an unknown integer-related | Aug 30, 2022 | 7.8 | 25 | NO | NO |
CVE-2019-13289HIGH In Xpdf 4.01.01, there is a use-after-free vulnerability in the function JBIG2Stream::close() located at JBIG2Stream.cc. It can, for example, be triggered by sending a crafted PDF | Jul 4, 2019 | 7.8 | 25 | NO | NO |
CVE-2019-13283HIGH In Xpdf 4.01.01, a heap-based buffer over-read could be triggered in strncpy from FoFiType1::parse in fofi/FoFiType1.cc because it does not ensure the source string has a valid len | Jul 4, 2019 | 7.8 | 25 | NO | NO |
CVE-2019-13281HIGH In Xpdf 4.01.01, a heap-based buffer overflow could be triggered in DCTStream::decodeImage() in Stream.cc when writing to frameBuf memory. It can, for example, be triggered by send | Jul 4, 2019 | 7.8 | 25 | NO | NO |
Signals from CVEs in this vendor scope (56 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Glyphandcog.
Media articles that mention a CVE ID that affects a product developed by Glyphandcog — matched by CVE ID, not by vendor name.