CVE-2007-5392

HIGHCVSS v2 · 9.39.3
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:M/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 6.4% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 6.4%CVSS v2: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Integer overflow in the DCTStream::reset method in xpdf/Stream.cc in Xpdf 3.02p11 allows remote attackers to execute arbitrary code via a crafted PDF file, resulting in a heap-based buffer overflow.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3HIGHlow confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation6.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
6.4%
EPSS %ILE
93rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 8, 2007

Last Modified

April 23, 2026

References (82)

15 of 82 shown · show the other 67

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibpoppler2 (0.6-0ubuntu2.1) @ gutsy2026-05-31ubuntu
ubuntukword (1:1.6.3-0ubuntu5.1) @ gutsy2026-05-31ubuntu
redhatkdegraphics-7:3.3.1-6.el4_52007-11-12redhat
redhattetex-0:3.0-33.2.el5_1.22007-11-08redhat
redhatxpdf-1:3.00-14.el42007-11-07redhat
redhatcups-1:1.2.4-11.14.el5_1.32007-11-07redhat
redhatpoppler-0:0.5.4-4.3.el5_12007-11-07redhat
redhatcups-1:1.1.22-0.rc1.9.20.2.el4_5.22007-11-07redhat
redhatxpdf-1:2.02-11.el32007-11-07redhat
redhatgpdf-0:2.8.2-7.7.12007-11-07redhat

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.

Affected Packages

(21 across 6 ecosystems)
Debian:11(4)
PackageVulnerable rangeFix by version rangeDependents
cups—
  • every version up to 1.1.22-7: fixed in 1.1.22-7
—
libextractor—
  • every version up to 0.5.12-1: fixed in 0.5.12-1
—
poppler—
  • every version up to 0.6.2-1: fixed in 0.6.2-1
—
xpdf—
  • every version up to 3.02-1.3: fixed in 3.02-1.3
—
Debian:12(4)
PackageVulnerable rangeFix by version rangeDependents
cups—
  • every version up to 1.1.22-7: fixed in 1.1.22-7
—
libextractor—
  • every version up to 0.5.12-1: fixed in 0.5.12-1
—
poppler—
  • every version up to 0.6.2-1: fixed in 0.6.2-1
—
xpdf—
  • every version up to 3.02-1.3: fixed in 3.02-1.3
—
Debian:13(4)
PackageVulnerable rangeFix by version rangeDependents
cups—
  • every version up to 1.1.22-7: fixed in 1.1.22-7
—
libextractor—
  • every version up to 0.5.12-1: fixed in 0.5.12-1
—
poppler—
  • every version up to 0.6.2-1: fixed in 0.6.2-1
—
xpdf—
  • every version up to 3.02-1.3: fixed in 3.02-1.3
—
Debian:14(4)
PackageVulnerable rangeFix by version rangeDependents
cups—
  • every version up to 1.1.22-7: fixed in 1.1.22-7
—
libextractor—
  • every version up to 0.5.12-1: fixed in 0.5.12-1
—
poppler—
  • every version up to 0.6.2-1: fixed in 0.6.2-1
—
xpdf—
  • every version up to 3.02-1.3: fixed in 3.02-1.3
—
Debian:4.0(3)
PackageVulnerable rangeFix by version rangeDependents
koffice1:1.6.1-2, 1:1.6.1-2etch1
  • every version up to 1:1.6.1-2etch2: fixed in 1:1.6.1-2etch2
—
poppler0.4.5-5.1, 0.4.5-5.1etch1
  • every version up to 0.4.5-5.1etch2: fixed in 0.4.5-5.1etch2
—
xpdf3.01-9, 3.01-9etch1
  • every version up to 3.01-9.1+etch2: fixed in 3.01-9.1+etch2
—
Debian:5.0(2)
PackageVulnerable rangeFix by version rangeDependents
kdegraphics—
  • every version up to 4:3.5.7-4+lenny1: fixed in 4:3.5.7-4+lenny1
—
koffice—
  • every version up to 1:1.6.3-3+lenny1: fixed in 1:1.6.3-3+lenny1
—

Weakness Classification(1)

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

All Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 84 of 120 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 16 repeat rows among the latest 100 are merged into the row they repeat. The 36 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 02:04 UTCEG score recompute
  2. 2026-10-11 13:37 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  3. 2026-10-10 19:53 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  5. 2026-10-08 16:33 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  6. 2026-10-07 23:37 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  7. 2026-10-06 15:09 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  8. 2026-10-05 17:37 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  9. 2026-10-04 23:15 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  10. 2026-10-04 08:07 UTCOSV refresh
  11. 2026-10-03 14:20 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  12. 2026-10-01 19:42 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  13. 2026-09-30 14:57 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  14. 2026-09-29 07:44 UTCEG score recompute
  15. 2026-09-18 19:20 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  16. 2026-09-17 19:20 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  17. 2026-09-15 03:04 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  18. 2026-09-14 22:44 UTCOSV refresh
  19. 2026-09-12 14:54 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  20. 2026-09-05 15:22 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  21. 2026-09-04 13:55 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  22. 2026-09-04 04:59 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  23. 2026-08-30 01:14 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  24. 2026-08-26 22:03 UTCOSV refresh
  25. 2026-08-10 12:10 UTCOSV refresh
Show 59 more
  1. 2026-08-08 16:30 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  2. 2026-08-07 16:20 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  3. 2026-08-06 13:41 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  4. 2026-08-05 19:11 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  5. 2026-08-04 15:03 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  6. 2026-08-03 10:28 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  7. 2026-07-30 16:22 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  8. 2026-07-30 01:25 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  9. 2026-07-28 15:30 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  10. 2026-07-26 13:33 UTCEG score recomputeFirst assessed: 9.3 HIGH
  11. 2026-07-25 14:12 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  12. 2026-07-25 12:41 UTCOSV refresh
  13. 2026-07-24 14:11 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  14. 2026-07-23 14:13 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  15. 2026-07-23 00:54 UTCEG score recompute
  16. 2026-07-23 00:33 UTCEG score recompute
  17. 2026-07-22 23:59 UTCEG score recompute
  18. 2026-07-22 21:38 UTCEG score recompute
  19. 2026-07-22 14:03 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  20. 2026-07-21 15:19 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  21. 2026-07-20 17:03 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  22. 2026-07-18 09:59 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  23. 2026-07-16 16:58 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  24. 2026-07-15 16:54 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  25. 2026-07-15 01:55 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  26. 2026-07-13 06:07 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  27. 2026-07-11 08:22 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  28. 2026-07-08 15:09 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  29. 2026-07-08 07:35 UTCOSV refresh
  30. 2026-07-06 16:22 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  31. 2026-07-06 02:19 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  32. 2026-07-05 02:26 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  33. 2026-07-04 06:27 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  34. 2026-07-02 14:00 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  35. 2026-07-01 15:02 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  36. 2026-06-30 23:19 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  37. 2026-06-29 14:02 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  38. 2026-06-28 14:03 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  39. 2026-06-28 04:52 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  40. 2026-06-27 03:04 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  41. 2026-06-25 13:46 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  42. 2026-06-24 14:02 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  43. 2026-06-23 21:29 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  44. 2026-06-22 14:22 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  45. 2026-06-21 01:56 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  46. 2026-06-19 19:25 UTCOSV refresh
  47. 2026-06-19 19:22 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  48. 2026-06-18 17:49 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  49. 2026-06-17 17:49 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  50. 2026-06-16 17:49 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  51. 2026-06-15 17:44 UTCEPSS rescoreEPSS 6.4% · 92nd percentile
  52. 2026-06-13 22:57 UTCEPSS rescoreEPSS 6.5% · 91st percentile
  53. 2026-06-12 23:08 UTCEPSS rescoreEPSS 6.5% · 91st percentile
  54. 2026-06-10 22:14 UTCEPSS rescoreEPSS 6.5% · 91st percentile
  55. 2026-06-10 13:17 UTCEPSS rescoreEPSS 6.5% · 91st percentile
  56. 2026-06-08 14:13 UTCEPSS rescoreEPSS 6.5% · 91st percentile
  57. 2026-06-07 15:21 UTCEPSS rescoreEPSS 6.6% · 91st percentile
  58. 2026-06-06 13:44 UTCEPSS rescoreEPSS 6.6% · 91st percentile
  59. 2026-06-05 22:44 UTCEPSS rescoreEPSS 6.6% · 91st percentile

Frequently asked(4)

What is CVE-2007-5392?
CVE-2007-5392 is a high-severity vulnerability; its CVE record was published on November 8, 2007. Integer overflow in the DCTStream::reset method in xpdf/Stream.cc in Xpdf 3.02p11 allows remote attackers to execute arbitrary code via a crafted PDF file, resulting in a heap-based buffer overflow.
When was CVE-2007-5392 made public?
CVE-2007-5392 was made public on November 7, 2007: that is the date its CVE record's CNA, Flexera Software LLC, gives for when the vulnerability was made public. The CVE record itself was published on November 8, 2007. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2007-5392 actively exploited?
CVE-2007-5392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.4% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-5392?
A fix for CVE-2007-5392 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2007-5392

Explore →

Is Your Infrastructure Affected by CVE-2007-5392?

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