CVE-2026-56002

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

A heap bufferflow in pcfReadFont() due to missing glyph bounds checking in libXfont2 before 2.0.8  allows attackers authenticated as X client to execute code within the X server.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 13, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

oss-security - FW: X.Org Security Advisory: multiple security issues in libXfont2

https://www.openwall.com/lists/oss-security/2026/07/08/1
generic

pcfread: validate bitmap sizes and offsets against per-glyph metrics (b4389e0b) · Commits · xorg / lib / libXfont · GitLab

https://gitlab.freedesktop.org/xorg/lib/libxfont/-/commit/b4389e0b1d84a690b819bb27b1439968811a3674

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibxfont2 (1:2.0.3-1ubuntu0.20.04.1~esm2) @ focal2026-09-18ubuntu
redhatlibXfont2-0:2.0.3-12.el9_6.12026-08-06redhat
redhatlibXfont2-0:2.0.3-2.el8_8.12026-08-06redhat
redhatlibXfont2-0:2.0.3-2.el8_6.12026-08-06redhat
redhatlibXfont2-0:2.0.3-12.el9_4.12026-08-06redhat
redhatlibXfont2-0:2.0.6-5.el10_0.12026-08-06redhat
redhatlibXfont2-0:2.0.3-2.el7_92026-08-06redhat
redhatlibXfont2-0:2.0.3-12.el9_2.12026-08-06redhat
redhatlibXfont2-0:2.0.3-2.el8_4.12026-08-06redhat
redhatlibXfont2-0:2.0.3-12.el9_8.12026-08-03redhat
redhatlibXfont2-0:2.0.3-2.el8_10.12026-07-28redhat
redhatlibXfont2-0:2.0.6-5.el10_2.12026-07-28redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libxfont1:2.0.4-11:2.0.4-1+deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxfont1:2.0.6-11:2.0.6-1+deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxfont1:2.0.6-11:2.0.6-1+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxfont1:2.0.6-1, 1:2.0.6-1+hurd.1, 1:2.0.6-21:2.0.8-1

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 9× in last 7d / 73× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 276 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 05:46 UTCEG score recompute
  4. 2026-09-18 05:46 UTCVendor advisory
  5. 2026-09-18 05:46 UTCGHSA enrichment
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 03:11 UTCEPSS rescore
  10. 2026-09-13 23:51 UTCEG score recompute
  11. 2026-09-13 23:51 UTCVendor advisory
  12. 2026-09-13 23:51 UTCGHSA enrichment
  13. 2026-09-13 16:47 UTCEPSS rescore
  14. 2026-09-13 08:27 UTCVendor advisory
  15. 2026-09-13 08:27 UTCGHSA enrichment
  16. 2026-09-12 16:45 UTCEG score recompute
  17. 2026-09-12 16:45 UTCVendor advisory
  18. 2026-09-12 16:45 UTCGHSA enrichment
  19. 2026-09-12 03:39 UTCEG score recompute
  20. 2026-09-12 03:39 UTCVendor advisory
  21. 2026-09-12 03:39 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-10 09:35 UTCEPSS rescore
  24. 2026-09-08 22:01 UTCEPSS rescore
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 14:06 UTCEG score recompute
  2. 2026-09-06 14:06 UTCVendor advisory
  3. 2026-09-06 14:06 UTCGHSA enrichment
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-05 22:50 UTCEG score recompute
  6. 2026-09-05 22:50 UTCVendor advisory
  7. 2026-09-05 22:50 UTCGHSA enrichment
  8. 2026-09-04 05:07 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 20:30 UTCEG score recompute
  13. 2026-08-30 20:30 UTCVendor advisory
  14. 2026-08-30 20:30 UTCGHSA enrichment
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 07:38 UTCEG score recompute
  17. 2026-08-30 07:38 UTCVendor advisory
  18. 2026-08-30 07:38 UTCGHSA enrichment
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 21:52 UTCEG score recompute
  22. 2026-08-27 21:52 UTCVendor advisory
  23. 2026-08-27 21:52 UTCGHSA enrichment
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-27 01:45 UTCEG score recompute
  26. 2026-08-27 01:45 UTCVendor advisory
  27. 2026-08-27 01:45 UTCGHSA enrichment
  28. 2026-08-26 14:46 UTCEPSS rescore
  29. 2026-08-26 08:30 UTCEG score recompute
  30. 2026-08-26 08:30 UTCVendor advisory
  31. 2026-08-26 08:30 UTCGHSA enrichment
  32. 2026-08-25 13:49 UTCEPSS rescore
  33. 2026-08-25 11:51 UTCVendor advisory
  34. 2026-08-25 11:51 UTCGHSA enrichment
  35. 2026-08-24 22:52 UTCEG score recompute
  36. 2026-08-24 22:52 UTCVendor advisory
  37. 2026-08-24 22:52 UTCGHSA enrichment
  38. 2026-08-24 10:01 UTCEG score recompute
  39. 2026-08-24 10:01 UTCVendor advisory
  40. 2026-08-24 10:01 UTCGHSA enrichment
  41. 2026-08-23 21:08 UTCVendor advisory
  42. 2026-08-23 21:08 UTCGHSA enrichment
  43. 2026-08-23 08:16 UTCEG score recompute
  44. 2026-08-23 08:16 UTCVendor advisory
  45. 2026-08-23 08:16 UTCGHSA enrichment
  46. 2026-08-23 00:19 UTCEPSS rescore
  47. 2026-08-22 19:17 UTCVendor advisory
  48. 2026-08-22 19:17 UTCGHSA enrichment
  49. 2026-08-22 06:25 UTCEG score recompute
  50. 2026-08-22 06:25 UTCVendor advisory
  51. 2026-08-22 06:25 UTCGHSA enrichment
  52. 2026-08-21 23:49 UTCEPSS rescore
  53. 2026-08-21 17:22 UTCVendor advisory
  54. 2026-08-21 17:22 UTCGHSA enrichment
  55. 2026-08-21 04:30 UTCEG score recompute
  56. 2026-08-21 04:30 UTCVendor advisory
  57. 2026-08-21 04:30 UTCGHSA enrichment
  58. 2026-08-20 22:55 UTCEPSS rescore
  59. 2026-08-20 15:38 UTCVendor advisory
  60. 2026-08-20 15:38 UTCGHSA enrichment
  61. 2026-08-20 02:06 UTCEG score recompute
  62. 2026-08-20 02:06 UTCVendor advisory
  63. 2026-08-20 02:06 UTCGHSA enrichment
  64. 2026-08-19 17:04 UTCEPSS rescore
  65. 2026-08-19 09:48 UTCVendor advisory
  66. 2026-08-19 09:48 UTCGHSA enrichment
  67. 2026-08-18 20:46 UTCEG score recompute
  68. 2026-08-18 20:46 UTCVendor advisory
  69. 2026-08-18 20:46 UTCGHSA enrichment
  70. 2026-08-18 13:48 UTCEPSS rescore
  71. 2026-08-18 04:52 UTCVendor advisory
  72. 2026-08-18 04:52 UTCGHSA enrichment
  73. 2026-08-17 16:00 UTCEG score recompute
  74. 2026-08-17 16:00 UTCVendor advisory
  75. 2026-08-17 16:00 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56002?
CVE-2026-56002 is a high vulnerability published on July 8, 2026. A heap bufferflow in pcfReadFont() due to missing glyph bounds checking in libXfont2 before 2.0.8 allows attackers authenticated as X client to execute code within the X server.
When was CVE-2026-56002 disclosed?
CVE-2026-56002 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56002 actively exploited?
CVE-2026-56002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.4% of all scored CVEs.
What is the CVSS score of CVE-2026-56002?
CVE-2026-56002 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-56002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56002, 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-2026-56002

Explore →

Is Your Infrastructure Affected by CVE-2026-56002?

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