# CVE-2026-15370: Libssh: libssh: stack buffer overflow in sftp server longname construction

> A stack buffer overflow in libssh's SFTP server allows attackers to cause crashes or execute code via long filenames.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-15370, DEBIAN-CVE-2026-15370, ECHO-b5b0-c714-39f4, GHSA-6j7f-8jjp-mm8c, MINI-p4h2-gw6w-9259, RHSA-2026:47768, UBUNTU-CVE-2026-15370

## What is CVE-2026-15370?

CVE-2026-15370 is a medium-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 21 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### 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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-15370?

It affects 11 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libssh` | Red Hat:hummingbird:1 | All versions | 0:0.12.2-1.hum1 |
| `libssh-config` | Red Hat:hummingbird:1 | All versions | 0:0.12.2-1.hum1 |
| `libssh-devel` | Red Hat:hummingbird:1 | All versions | 0:0.12.2-1.hum1 |

Products: Libssh Libssh, Redhat Enterprise Linux, Redhat Enterprise Linux for Els, Redhat Enterprise Linux for Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Els, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Power Little Endian Els, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Hardened Images.

## How do I fix CVE-2026-15370?

Apply the vendor's patch.

## Is CVE-2026-15370 being exploited?

There is no known exploitation of CVE-2026-15370 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2026-59851](https://insights.sbomify.com/CVE-2026-59851/): Libssh: libssh: authentication bypass via missing gssapi principal check (high 8.8)
- [CVE-2025-5987](https://insights.sbomify.com/CVE-2025-5987/): Libssh: invalid return code for chacha20 poly1305 with openssl backend (high 8.1)
- [CVE-2025-14821](https://insights.sbomify.com/CVE-2025-14821/): Libssh: libssh: insecure default configuration leads to local man-in-the-middle attacks on windows (high 7.8)
- [CVE-2012-4560](https://insights.sbomify.com/CVE-2012-4560/): Memory corruption in n/a (high 7.5)
- [CVE-2012-4562](https://insights.sbomify.com/CVE-2012-4562/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15370 and fix it if it is affected.

What it is: CVE-2026-15370 is a medium-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 21 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-15370 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15370/ (Markdown: https://insights.sbomify.com/CVE-2026-15370/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15370
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15370
- OSV: https://osv.dev/vulnerability/CVE-2026-15370

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15370/
Summaries are generated and may contain mistakes; the official description above is the record.