CVE-2026-59679: libXfont2 Out-of-Bounds Write
CVE-2026-59679 is a critical out-of-bounds write vulnerability in libXfont2, published in the National Vulnerability Database (NVD) on September 10, 2026. It carries a CVSS v3.1 base score of 9.0 (Critical). According to its CVSS vector, it can be exploited over the network, needs no privileges and no user interaction.
What is CVE-2026-59679?
libXfont2's fs_read_glyphs can lead to out-of-bounds reads and writes via font server replies.
The NVD description reads:
fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) indexes the per-character encoding[] array using num_chars from the FS_QueryXBitmaps16 reply, but that array was allocated with a size derived from num_extents in the separate FS_QueryXExtents16 reply. The two CARD32 fields are never cross-checked. A malicious or compromised font server can send a small num_extents (e.g. 1) in the extents reply, then a large num_chars (e.g. 100000) in the bitmaps reply. This causes attacker-controlled out-of-bounds heap read and writes.
NVD maps this issue to CWE-787 (Out-of-bounds Write).
Affected versions and packages
NVD does not publish structured version ranges for CVE-2026-59679 at the time of writing, so check the description above and the vendor advisory in the references for the exact affected releases.
Echo's advisory data tracks 1 package for CVE-2026-59679: libxfont2.
Package versions listed in Echo's advisory data for this CVE (compare them with the versions you run):
- libxfont2: 1:2.0.6-1+b3, 1:2.0.6-1+deb13u1
Severity and CVSS score
A score of 9.0 puts CVE-2026-59679 in the Critical range (9.0 to 10.0), the highest CVSS band. The vector shows the attack path and the impact on confidentiality, integrity and availability. For help weighing exploit likelihood against raw severity, see our guide to patching AI-found zero-days before disclosure.
Impact: Out-of-Bounds Write
The CVSS vector rates the impact on confidentiality as high, integrity as high and availability as high. The scope is changed, meaning a successful attack can affect resources beyond the vulnerable component. Exploitation requires no privileges and no user interaction, and the attacker reaches the target over the network.
What this means in practice depends on how libXfont2 is used in your environment: how widely it is deployed, whether the affected code path is reachable, and what the process can access. Treat the exposed systems that run a listed version as in scope until you have confirmed otherwise.
Is CVE-2026-59679 being exploited in the wild?
Known exploitation: CISA KEV
No. As of November 4, 2026, CVE-2026-59679 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog (catalog version 2026.11.03). KEV only lists vulnerabilities with confirmed exploitation, so absence from the catalog is not proof that nobody is exploiting the flaw.
EPSS score and percentile
The Exploit Prediction Scoring System (EPSS) from FIRST estimates the probability that a CVE will see exploitation activity in the next 30 days. On November 3, 2026, CVE-2026-59679 had an EPSS score of 0.003, which corresponds to a probability of 0.26%. It sits at the 17th percentile, which means it is scored as more likely to be exploited than roughly 17% of scored CVEs, placing it below the median of scored CVEs. EPSS is recalculated daily and is a likelihood estimate, not a confirmation, so read it together with KEV status, exposure and CVSS severity.
Attack vector, complexity, privileges and user interaction
Based on the CVSS v3.1 vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H (source: CNA), this is how an attacker has to approach CVE-2026-59679:
- Attack vector: Network (AV:N): the flaw can be reached remotely over the network, so the attacker does not need to be on the same host or LAN.
- Attack complexity: High (AC:H): success depends on conditions outside the attacker's control, such as a specific configuration, timing or extra preparation, which makes reliable exploitation harder.
- Privileges required: None (PR:N): no account or credentials are needed.
- User interaction: None (UI:N): no action by a user is required.
- Scope: Changed (S:C): a successful attack can affect resources beyond the vulnerable component.
Is there a public proof of concept or exploit?
CISA's SSVC assessment recorded in NVD (dated September 10, 2026) lists the exploitation status as "none", which means there was no evidence of active exploitation and no public proof of concept at that time. None of the references in the NVD record is tagged as an exploit. This reflects NVD and CISA records as of November 4, 2026, and public exploit code can appear at any time.
Practical exposure conditions
- Only systems that run an affected version are exposed. Compare the libXfont2 versions in your hosts and container images against the versions listed in the Echo advisory data and the vendor advisory above.
- The vector is network-based, so libXfont2 deployments that process input from untrusted networks carry the most risk, especially internet-facing ones. Internal-only deployments are still exposed to anyone who can reach them.
- No credentials are needed, so exposure does not depend on how well accounts are protected.
- No user has to click or open anything, so the flaw can be triggered without any user action.
- Exploitation depends on additional conditions, which can lower the practical risk for hardened or unusual configurations, but it does not remove the need to patch.
- The scope is changed, so a successful attack can reach beyond the vulnerable component.
- CISA's SSVC assessment marks the issue as not automatable, which means attacks are harder to run at scale.
How to fix CVE-2026-59679
- Inventory. Find every host, container image and base image that includes libXfont2, including the packages listed above (libxfont2).
- Upgrade. Upgrade to the release that the vendor or your distribution lists as fixed for CVE-2026-59679. The references below link to the upstream advisory.
- Rebuild and restart. Rebuild container images and restart the services that load libXfont2 so the patched code is actually used.
- Verify. Re-scan your images and hosts to confirm that no package still matches a vulnerable version of CVE-2026-59679.
Interim mitigations if you cannot patch immediately
These are general hardening steps, not a vendor-specific workaround. Updating is the only complete fix.
- Restrict network access to services that use libXfont2 to trusted sources with firewall rules or allow-lists until you can patch.
- Monitor logs and runtime behavior on affected systems for unusual activity, and prioritize them in your next patch window.
How Echo helps with CVE-2026-59679
Echo is a registered CVE Numbering Authority (CNA) and ships patched, vetted open source packages and container images, so teams can remove vulnerable components instead of tracking an endless backlog. For this CVE, Echo's advisory data tracks 1 package (libxfont2). Read how automated patch SLAs reduce enterprise risk in how automated patch SLAs reduce enterprise risk and why how to deal with CVE backlogs matters. Related libXfont2 advisories: CVE-2026-44950.
Frequently asked questions about CVE-2026-59679
What is CVE-2026-59679?
CVE-2026-59679 is a critical out-of-bounds write vulnerability in libXfont2. libXfont2's fs_read_glyphs can lead to out-of-bounds reads and writes via font server replies. It has a CVSS base score of 9.0.
Which versions are affected by CVE-2026-59679?
NVD does not publish structured version ranges for it yet. Echo's advisory data tracks these libXfont2 packages: libxfont2.
Is CVE-2026-59679 actively exploited?
It is not listed in CISA's KEV catalog as of November 4, 2026 (catalog version 2026.11.03), but that does not rule out exploitation. FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 0.26%, at the 17th percentile (November 3, 2026). On public exploit code: CISA's SSVC assessment in NVD (dated September 10, 2026) lists no public proof of concept.
How do I fix CVE-2026-59679?
Upgrade to the release that the vendor or your distribution lists as fixed for CVE-2026-59679. The references below link to the upstream advisory. Then rebuild images, restart affected services and re-scan to confirm the fix.
How severe is CVE-2026-59679?
It is rated Critical with a CVSS base score of 9.0. The vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H means it can be exploited over the network, with no privileges and no user interaction.
Are there other libXfont2 vulnerabilities I should patch?
Yes. Echo's advisory data also covers CVE-2026-44950. Patch them together to reduce the number of upgrade cycles.