🛡️ CVE-2026-56002 — libxfont

🟠 CVSS 8.5 — High ✅ No Known Exploit CWE-122 NVD
8.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality high, integrity high, availability high.

Weakness class

CVE-2026-56002 is classified as CWE-122: Heap-based Buffer Overflow. A write past the end of a heap allocation corrupts allocator metadata or neighbouring objects.

Affected software

CVE-2026-56002 is recorded against 1 package.

  • libxfont (fixed in 2.0.8)

Timeline and source

Published on 8 July 2026 and last revised on 13 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

gitlab.freedesktop.org
www.openwall.com

Details

Severity HIGH
CVSS Score 8.5
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
CWE CWE-122
Public Exploit ✅ No
Source NVD
Published 2026-07-08
Updated 2026-08-11
Modified 2026-07-13

Affected Packages

Software From version Fixed in
libxfont — 2.0.8

Site Security Check

Is libxfont part of your stack?

CVE-2026-56002 is rated CVSS 8.5 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.