libfontenc 1.1.10 patches a local-root font-parser flaw and a second bug in the same file
The tiny 15-KB library that renders text on most Linux desktops got a heap-write flaw patched today. The fix arrived bundled with another bug in the same 1998-era code, a memory-leak repair, and it was all part of a coordinated X.Org advisory.
The X.Org project shipped libfontenc 1.1.10 today, and the headline reason is a security patch. It plugs a heap out-of-bounds write in the library's .enc font-encoding parser. The flaw, CVE-2026-109908, can lead to local privilege escalation on Linux and Unix systems where the X server runs as root. On a typical multi-user desktop, that effectively means root.
It's about 15 KB. Small enough to forget, even though the library does the actual work of turning a font request into on-screen glyphs. When an X server loads a "core" font, the request passes through libfontenc, which maps raw character codes to the Unicode or PostScript values your app asked for. Virtually every traditional Linux desktop links it, either directly or through libXfont2.
The bug, and why the same file needed two fixes
The vulnerable code lives in setCode() inside src/encparse.c. The function computes a destination index using the formula (from >> 8) * row_size + (from & 0xFF), where row_size comes straight from the SIZE line of the encoding file and is never bounded. The buffer it writes into is hard-capped at 0x10000 entries. A crafted .enc file can push the index right past the end of that allocation.
X.Org's advisory is blunt about the mechanics: "A crafted .enc file makes the index exceed the allocation and writes past it."
That's a textbook out-of-bounds write. What's more interesting is the age of the code. This parser was originally written by Juliusz Chroboczek, MIT-licensed, sometime between 1998 and 2001. Two memory-safety bugs in the same file, fixed in a single release, suggests it hadn't seen tight bounds-checking review in a very long time.
The second bug is a heap overflow Peter Hutterer caught in the NAME_LINE handler, and it's the classic element-count-versus-bytes mixup. After the parser decides it needs 0x10000 pointer slots, the growth path calls realloc(nam, namsize), passing the element count as a byte count. On a 64-bit system, where a char * is 8 bytes, the array ends up roughly 8x too small. Writes to nam[value1] then spill past the allocation.
This one isn't CVE-numbered. It just rode in on what the release labels "a grab bag of misc fixes."
A coordinated advisory, not a lone finding
libfontenc 1.1.10 was announced alongside a broader X.Org advisory. The same day, X.Org also shipped libXfont2-2.0.10, which closes two separate flaws. CVE-2026-109909 is a PCF font parsing bug where a negative skip count wraps a buffer pointer backward. CVE-2026-109920 is arguably worse: it reads uninitialized heap memory via a bare malloc() with no else branch, and the advisory notes you can reach it with ordinary core-protocol requests. A vendor .pcf font simply renamed to .pfb is enough to trip it.
The libfontenc finding itself stays local. An attacker has to place both a font and a matching .enc file on a path the server actually reads. No network vector here.
X.Org doesn't publish an explicit CVSS base score for CVE-2026-109908, and NVD/MITRE hasn't surfaced a vector string either. Part of that is structural: NIST trimmed its CVE enrichment workload back in 2026, leaving a lot of identifiers without an official score. Qualitatively, though, a heap write in a root-run process that the advisory calls a "potential local privilege escalation" lands firmly in the High band.
Here's a bit of history that frames it. In August 2026, X.Org (again pushed by Hutterer) disclosed multiple heap overflows in libXfont2, all traced to an incomplete fix of the 2014-era CVE-2014-0210. Memory bugs in font parsing, patched through coordinated disclosure via ZDI, has become a recurring theme in this ecosystem.
The people worth naming: Adam Bedard reported CVE-2026-109908 through TrendAI's Zero Day Initiative, the vulnerability-buying program Trend Micro runs. Hutterer, based at Red Hat in Brisbane, wrote six of the seven commits in 1.1.10. Alan Coopersmith handled the release; he's been maintaining the library since around 2010 and is one of the steady forces behind this quiet corner of X.Org, where releases are measured in build-system cleanups and Y2038 flags.
Consider that the whole premise here, the X server running as root, is a bit of a relic. Modern Wayland-first setups often drop those privileges. Shared CI runners, VPSes, and older multi-user boxes still run it as root, and that's exactly where this bites.
What to do
Update libfontenc to 1.1.10 on any host running a classic X11 or Xwayland session that loads core fonts. Debian and Ubuntu ship it as libfontenc1; Fedora tracks plain libfontenc. Check what you're running with dpkg -l libfontenc1 or rpm -q libfontenc. Anything below 1.1.10 is vulnerable.
Do it at the same time as updating libXfont2 to 2.0.10. That closes the two sibling CVEs, which have easier vectors than the libfontenc flaw. There's no software workaround before the patch lands. The advisory's practical advice is to restrict who can write to font directories on the server font path and watch for X server crashes as a DoS indicator.
For source builds, grab the tarball from the X.Org archive and verify the SHA256 before compiling. The .tar.xz arrives at daa186a49e3cc2b6fc585ca09971351e6f010f618abc6a164eda82e42e4aa4d6.
Head here to the security advisory and the release announcement for the full diff and the rest of the coordinated CVE list.
