Buffer Overflow The advisory has been revoked - it doesn't affect any version of package libXfont2-devel (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL7-LIBXFONT2DEVEL-18582830
- published7 Aug 2026
- disclosed5 Aug 2026
Introduced: 5 Aug 2026
CVE-2026-44950 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:7.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libXfont2-devel package and not the libXfont2-devel package as distributed by RHEL.
fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) copies each glyph's bitmap into a single buffer. Existing checks validates only that the source slice (position, length) lies within the source bitmap buffer. It does not check whether the running destination cursor has exceeded the allocation.
A malicious font server can send overlapping source offsets -- for example 1000 glyphs each referencing {position:0, length:64} with nbytes=64. Each individual source range passes the existing validation, but the cumulative writes total 64000 bytes into a 64-byte destination buffer. This is a heap buffer overflow with attacker-controlled content.