CVE Vulnerabilities

CVE-2026-88807

Heap-based Buffer Overflow

Published: Sep 21, 2026 | Modified: Sep 22, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
8.3 IMPORTANT
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Ubuntu
MEDIUM

A heap overflow in libXrender before 0.9.13 in RenderQueryPictFormats could be used by malicious X servers to inject code into attached X clients.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

NameVendorStart VersionEnd Version
Red Hat Enterprise Linux 10RedHatlibXrender-0:0.9.11-8.el10_2.1*
Red Hat Enterprise Linux 10RedHatlibXrender-0:0.9.11-8.el10_3.1*
Red Hat Enterprise Linux 8RedHatlibXrender-0:0.9.10-8.el8_10*
Red Hat Enterprise Linux 9RedHatlibXrender-0:0.9.10-16.el9_8.2*
Red Hat Enterprise Linux 9RedHatlibXrender-0:0.9.10-17.el9_9.1*
LibxrenderUbuntudevel*
LibxrenderUbuntuesm-infra-legacy/trusty*
LibxrenderUbuntuesm-infra-legacy/xenial*
LibxrenderUbuntuesm-infra/bionic*
LibxrenderUbuntuesm-infra/focal*
LibxrenderUbuntujammy*
LibxrenderUbuntunoble*
LibxrenderUbunturesolute*
LibxrenderUbuntustonking*
LibxrenderUbuntuupstream*

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References