CVE-2026-15370 Red Hat Enterprise Linux 10 vulnerability
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.
Browse Linux security risksQuick answer
Red Hat Enterprise Linux 10 should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-15370 affects Red Hat Enterprise Linux 10 and involves denial of service. A remote or untrusted peer may consume excessive resources or crash the affected service. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Apply the Red Hat libssh security update for the installed RHEL 10 channel as soon as it is available; until then, limit SFTP access and prevent untrusted users from creating filenames used in server directory listings.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses Red Hat Enterprise Linux 10.
- Compare the installed package, build, firmware, or commit with the affected range in the linked vendor and NVD advisories.
- Apply the Red Hat libssh security update for the installed RHEL 10 channel as soon as it is available; until then, limit SFTP access and prevent untrusted users from creating filenames used in server directory listings.
- Until patched, limit untrusted files and peers, apply resource limits, and isolate the affected parser or service.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Red Hat Enterprise Linux 10; remove access that is not required.
- Review application, system, proxy, and audit logs for requests and behavior linked to the affected feature and CVE.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-15370 in place.
- Use a safe regression test to confirm the affected denial of service path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-15370?
Red Hat Enterprise Linux 10 should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.