CVE-2009-0800

NONECVSS 0.0Trending — 4 sources updated this week

0.0

Multiple "input validation flaws" in the JBIG2 decoder in Xpdf 3.02pl2 and earlier, CUPS 1.3.9 and earlier, Poppler before 0.10.6, and other products allow remote attackers to execute arbitrary code via a crafted PDF file.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 92.8%
KEV: Not listed

Published

April 23, 2009

Last Modified

April 23, 2026

References (84)

secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2009-04/msg00011.html
secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2009-05/msg00000.html
secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2009-07/msg00002.html
secalert@redhathttp://poppler.freedesktop.org/releases.html
secalert@redhathttp://rhn.redhat.com/errata/RHSA-2009-0458.html
secalert@redhathttp://secunia.com/advisories/34291
secalert@redhathttp://secunia.com/advisories/34481
secalert@redhathttp://secunia.com/advisories/34746
secalert@redhathttp://secunia.com/advisories/34755
secalert@redhathttp://secunia.com/advisories/34756
secalert@redhathttp://secunia.com/advisories/34852
secalert@redhathttp://secunia.com/advisories/34959
secalert@redhathttp://secunia.com/advisories/34963
secalert@redhathttp://secunia.com/advisories/34991
secalert@redhathttp://secunia.com/advisories/35037

Patch Availability(9)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
ubuntu	libpoppler-glib2 (0.6.4-1ubuntu3.2) @ hardy	2026-05-30	ubuntu
ubuntu	kword (1:1.6.3-7ubuntu6.1) @ jaunty	2026-05-30	ubuntu
redhat	tetex-0:2.0.2-22.0.1.EL4.16	2010-05-06	redhat
redhat	tetex-0:3.0-33.8.el5_5.5	2010-05-06	redhat
redhat	poppler-0:0.5.4-4.4.el5_3.9	2009-05-13	redhat
redhat	gpdf-0:2.8.2-7.7.2.el4_7.4	2009-04-30	redhat
redhat	xpdf-1:3.00-20.el4	2009-04-16	redhat
redhat	cups-1:1.3.7-8.el5_3.4	2009-04-16	redhat
redhat	kdegraphics-7:3.5.4-12.el5_3	2009-04-16	redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-20Improper Input Validation

All Vendor Advisories

(9)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-04 13:09 UTCepss_batch
2026-06-04 13:09 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:13 UTCepss_batch
2026-05-31 00:13 UTCepss_batch
2026-05-30 17:06 UTCEG score recompute
2026-05-30 17:06 UTCVendor advisory
2026-05-30 17:06 UTCGHSA enrichment
2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:25 UTCOSV refresh
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch

Frequently asked(4)

What is CVE-2009-0800?

CVE-2009-0800 is a none vulnerability published on April 23, 2009. Multiple "input validation flaws" in the JBIG2 decoder in Xpdf 3.02pl2 and earlier, CUPS 1.3.9 and earlier, Poppler before 0.10.6, and other products allow remote attackers to execute arbitrary code via a crafted PDF file.

When was CVE-2009-0800 disclosed?

CVE-2009-0800 was first published in the National Vulnerability Database on April 23, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2009-0800 actively exploited?

CVE-2009-0800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2009-0800?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-0800, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2009-0800

Explore →

Is Your Infrastructure Affected by CVE-2009-0800?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2009-0800

Published

Last Modified

References (84)

Patch Availability(9)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2009-0800?

Same vendor

Same CWE

CVE-2009-0800

📅 Published

🔄 Last Modified

🔗 References (84)

Patch Availability(9)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2009-0800?

🔗 Related CVEs(same vendor + same CWE)

Same vendor

Same CWE

Published

Last Modified

References (84)

Frequently asked(4)

Related CVEs(same vendor + same CWE)