PatchSiren cyber security CVE debrief
CVE-2026-15370 Red Hat CVE debrief
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. This issue affects users of libssh SFTP server functionality, who should assess the risk of directory listing with attacker-controlled filenames.
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 10
- CVSS
- MEDIUM 6.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-21
- Original CVE updated
- 2026-08-17
- Advisory published
- 2026-07-21
- Advisory updated
- 2026-08-17
Who should care
Users of libssh SFTP server functionality should assess the risk of directory listing with attacker-controlled filenames. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review compensating controls for exposed systems while remediation is scheduled and verified.
Technical summary
The libssh library has a vulnerability in its SFTP server directory listing functionality. The longname field is built using unsafe concatenation into a fixed-size stack buffer. This can lead to a stack buffer overflow when listing attacker-controlled filenames, potentially causing server crashes or code execution. Affected product context includes libssh SFTP server functionality. Users of libssh SFTP server functionality should assess the risk of directory listing with attacker-controlled filenames. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review compensating controls for exposed systems while remediation is scheduled and verified. The vulnerability affects users of libssh SFTP server functionality, who should assess the risk of directory listing with attacker-controlled filenames.
Defensive priority
Apply vendor patches or updates to libssh as soon as available. Review and limit SFTP server access to trusted clients. Monitor SFTP server logs for suspicious activity and track exceptions, retest remediated assets.
Recommended defensive actions
- Apply patches or updates to libssh
- Limit SFTP server access to trusted clients
- Monitor SFTP server logs for suspicious activity
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record was published on 2026-07-21T09:16:53.683Z and was last modified on 2026-07-22T18:16:55.260Z. The NVD entry is currently Undergoing Analysis. Affected product deployments should be confirmed to exist in managed environments and assigned an owner for follow-up. Official advisories or CVE records should be reviewed to validate affected scope, severity, and vendor guidance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-15370 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-15370
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-15370 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-15370
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/security/cve/CVE-2026-15370
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.