CyberSecBulletin
CVE-2026-15370NVD status: Analyzed

Red Hat Enterprise Linux 10: Stack-based Buffer Overflow

CVE-2026-15370 is a high-severity stack-based buffer overflow vulnerability in Red Hat Enterprise Linux 10 from Red Hat, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Libssh to 0.11.5 or a later version.
  2. Read the advisory on access.redhat.com for workarounds and exact fixed builds.
  3. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Hardened ImagesNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
LibsshLibssh0.11.0 up to, but not including, 0.11.5; 0.12.00.11.5
Red HatHardened ImagesNot specified in the recordNot stated
Red HatEnterprise Linux10.0; 10.2Not stated
Red HatEnterprise Linux For Els10.2Not stated
Red HatEnterprise Linux For EUS10.2Not stated
Red HatEnterprise Linux For IBM Z Systems10.0; 10.2Not stated
Red HatEnterprise Linux For IBM Z Systems Els10.2Not stated
Red HatEnterprise Linux For IBM Z Systems EUS10.2Not stated
Red HatEnterprise Linux For Power Little Endian10.0; 10.2Not stated
Red HatEnterprise Linux For Power Little Endian Els10.2Not stated
Red HatEnterprise Linux For Power Little Endian EUS10.2Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.7MediumCNA (redhat.com)
CVSS 3.17.3HighNVD

Official description

A flaw was found in libssh. During SFTP server directory listing, the longname field is constructed with unsafe concatenation into a fixed-size stack buffer. When a client causes the server to list attacker-controlled filenames, sufficiently long names can overflow that stack buffer and may lead to crashes or possible code execution on the server.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Stack-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the stack.

How developers prevent this class of flaw

  • 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 discusses canary-based detection in detail.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implement and perform bounds checking on input.

More Stack-based Buffer Overflow vulnerabilities (CWE-121)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Red Hat Enterprise Linux 10

All Red Hat Enterprise Linux 10 vulnerabilities

Recent Stack-based Buffer Overflow vulnerabilities

Spotted an error? Tell us.