Most recent entries from all https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 20:36:31 +0000 CVE-2026-44950 — fs_read_glyphs() heap buffer overflow via cumulative glyph data overflow in libXfont2 https://vulnerability.circl.lu/vuln/cve-2026-44950 <p><strong>Affected:</strong> SUSE Container suse/kiosk/tigervnc-x11vnc:1.14-63.8, SUSE Container suse/kiosk/xorg:21.1-83.7, SUSE Image SLES15-SP6-SAP, SUSE Image SLES15-SP6-SAP-Azure, SUSE Image SLES15-SP6-SAP-Azure-3P, SUSE Image SLES15-SP6-SAP-BYOS, SUSE Image SLES15-SP6-SAP-BYOS-Azure, SUSE Image SLES15-SP6-SAP-BYOS-EC2, SUSE Image SLES15-SP6-SAP-BYOS-GCE, SUSE Image SLES15-SP6-SAP-EC2 and 70 more</p> <p>fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) copies each glyph&#39;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.</p> <p>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.</p> <p><strong>Affected:</strong> SUSE Container suse/kiosk/tigervnc-x11vnc:1.14-63.8, SUSE Container suse/kiosk/xorg:21.1-83.7, SUSE Image SLES15-SP6-SAP, SUSE Image SLES15-SP6-SAP-Azure, SUSE Image SLES15-SP6-SAP-Azure-3P, SUSE Image SLES15-SP6-SAP-BYOS, SUSE Image SLES15-SP6-SAP-BYOS-Azure, SUSE Image SLES15-SP6-SAP-BYOS-EC2, SUSE Image SLES15-SP6-SAP-BYOS-GCE, SUSE Image SLES15-SP6-SAP-EC2 and 70 more</p> <p>fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) copies each glyph&#39;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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-44950