CVE-2026-56002

HIGHPre-NVD 8.58.5
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. a secondary CVSS source baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5
EG Score
8.5(high)
EPSS
41.0%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 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

Vendor Advisories for CVE-2026-56002(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 27× 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.

  1. 2026-07-13 05:49 UTCEG score recompute
  2. 2026-07-13 05:49 UTCGHSA enrichment
  3. 2026-07-12 16:58 UTCEG score recompute
  4. 2026-07-12 16:58 UTCGHSA enrichment
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-12 04:06 UTCEG score recompute
  7. 2026-07-12 04:06 UTCGHSA enrichment
  8. 2026-07-11 15:14 UTCEG score recompute
  9. 2026-07-11 15:14 UTCGHSA enrichment
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 02:22 UTCEG score recompute
  13. 2026-07-11 02:22 UTCGHSA enrichment
  14. 2026-07-10 13:30 UTCEG score recompute
  15. 2026-07-10 13:30 UTCGHSA enrichment
  16. 2026-07-10 00:38 UTCEG score recompute
  17. 2026-07-10 00:38 UTCGHSA enrichment
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 11:45 UTCEG score recompute
  21. 2026-07-09 11:45 UTCGHSA enrichment
  22. 2026-07-08 22:52 UTCEG score recompute
  23. 2026-07-08 22:52 UTCGHSA enrichment
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 15:16 UTCEPSS rescore
Show 2 more
  1. 2026-07-08 10:01 UTCEG score recompute
  2. 2026-07-08 10:00 UTCMITRE cvelistV5first tracked

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 9, 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 41.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56002?
CVE-2026-56002 has a CVSS v3 base score of 8.5 (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

Explore the affected products and dependency analysis for 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.