Loading vulnerability…
CVE-2026-56002 is a heap-based buffer overflow in libXfont2 before version 2.0.8 in the pcfReadFont() function while parsing PCF fonts. The flaw arises because the repadded bitmap buffer is allocated using a bitmapSizes[] value taken directly from the PCF file without cross-validation against per-glyph metrics, and subsequent writes into that buffer also rely on unvalidated glyph-derived size information. A crafted PCF font can declare an undersized bitmapSizes[] entry for the server's glyph pad index while supplying glyph metrics that cause writes beyond the allocated heap buffer. The vulnerability can be triggered during font parsing without requiring rendering, resulting in memory corruption in the X server font handling path.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A heap buffer overflow in libXfont2's pcfReadFont() caused by missing glyph bounds checking, allowing authenticated X clients to execute code within the X server.
One of three vulnerabilities fixed in libXfont 2.0.8 related to processing PCF font files.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.