CVE-2026-56002 is a heap-based buffer overflow in libXfont2 versions before 2.0.8. In pcfReadFont(), the repadded bitmap buffer is sized from a bitmap-size value supplied by a PCF font without validating it against attacker-controlled per-glyph metrics. A malicious PCF font can declare an undersized bitmap allocation while providing glyph metrics and bitmap data that cause writes beyond that allocation. The flaw can be triggered during PCF font parsing and does not require font rendering.
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.
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by Huawei's EulerOS SA-2026-3272 advisory for libxfont2-related packages. The content provides no technical flaw description or CVSS score specifically attributable to this CVE.
A vulnerability addressed by the Huawei EulerOS SA-2026-3347 security update for libxfont2 packages. The content provides no technical flaw description.
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.