CVE Vulnerabilities

CVE-2026-5713

Stack-based Buffer Overflow

Published: Apr 14, 2026 | Modified: Jun 10, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
6 MODERATE
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

The profiling.sampling module (Python 3.15+) and asyncio introspection capabilities (3.14+, python -m asyncio ps and python -m asyncio pstree) features could be used to read and write addresses in a privileged process if that process connected to a malicious or infected Python process via the remote debugging feature. This vulnerability requires persistently and repeatedly connecting to the process to be exploited, even after the connecting process crashes with high likelihood due to ASLR.

Weakness

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Affected Software

NameVendorStart VersionEnd Version
Red Hat Enterprise Linux 10RedHatpython3.14-0:3.14.4-2.el10_2*
Red Hat Enterprise Linux 9RedHatpython3.14-0:3.14.4-2.el9_8*
Red Hat Hardened ImagesRedHatpython3-13-main-3.13.13-1.hum1*
Red Hat Hardened ImagesRedHatpython3-11-main-3.11.15-4.hum1*
Red Hat Hardened ImagesRedHatpython3-12-main-3.12.13-3.hum1*
Red Hat Hardened ImagesRedHatpython3-14-main-3.14.4-2.hum1*
Python2.7Ubuntuesm-infra/xenial*
Python3.14Ubuntudevel*
Python3.14Ubuntuupstream*
Python3.5Ubuntuesm-infra/xenial*

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