RHSA-2026:62218: Moderate: libssh security update

Published Sep 1, 2026
·
Updated

libssh is a library which implements the SSH protocol. It can be used to implement client and server applications.Security Fix(es): libssh: libssh: denial of service via zero advertised channel packet size (CVE-2026-59843) libssh: libssh: denial of service via oversized SFTP read length (CVE-2026-59844) libssh: libssh: denial of service via unchecked ProxyCommand fork() failure (CVE-2026-59845) libssh: libssh: information disclosure via ProxyCommand %r username expansion (CVE-2026-59846) libssh: libssh: integrity downgrade via OpenSSL AES-GCM tag verification (CVE-2026-59847) libssh: libssh: denial of service via SFTP responses with unknown request IDs (CVE-2026-59848) libssh: libssh: use-after-free via data callbacks on closed channels (CVE-2026-59850) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Affected Software

17 affected componentsFixes available
redhat/libssh<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-config<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-debuginfo<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-debuginfo<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-debugsource<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-debugsource<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-devel<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-devel<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-debuginfo<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-debugsource<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh-devel<0.9.6-17.el8_10
0.9.6-17.el8_10
redhat/libssh<0.9.6-17.el8_10.aa
0.9.6-17.el8_10.aa
redhat/libssh-debuginfo<0.9.6-17.el8_10.aa
0.9.6-17.el8_10.aa
redhat/libssh-debugsource<0.9.6-17.el8_10.aa
0.9.6-17.el8_10.aa
redhat/libssh-devel<0.9.6-17.el8_10.aa
0.9.6-17.el8_10.aa

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/libssh to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10
  2. Upgrade

    Upgrade redhat/libssh-config to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10
  3. Upgrade

    Upgrade redhat/libssh-debuginfo to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10
  4. Upgrade

    Upgrade redhat/libssh-debugsource to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10
  5. Upgrade

    Upgrade redhat/libssh-devel to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10
  6. Upgrade

    Upgrade redhat/libssh to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10.aa
  7. Upgrade

    Upgrade redhat/libssh-debuginfo to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10.aa
  8. Upgrade

    Upgrade redhat/libssh-debugsource to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10.aa
  9. Upgrade

    Upgrade redhat/libssh-devel to a version that resolves this vulnerability.

    Fixed in 0.9.6-17.el8_10.aa

Event History

Sep 1, 2026
Advisory Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionAffected Software

Frequently Asked Questions

1

Which applications are potentially exposed to these issues?

Applications that use libssh to implement SSH client or server functionality may be affected. The listed fixes also specifically involve SFTP handling, ProxyCommand processing, SSH channel callbacks, and OpenSSL AES-GCM tag verification.

2

What attacker-controlled conditions are involved in the denial-of-service issues?

The described denial-of-service conditions involve a zero advertised channel packet size, an oversized SFTP read length, SFTP responses containing unknown request IDs, and an unchecked ProxyCommand fork() failure. Whether an attacker can trigger a given condition depends on whether the application uses the affected libssh feature or protocol path.

3

Are ProxyCommand users subject to risks beyond denial of service?

Yes. One listed issue discloses information through ProxyCommand %r username expansion, while another can cause denial of service when ProxyCommand fork() failures are unchecked. These risks are relevant where the application uses libssh ProxyCommand functionality.

4

Does the update address an integrity-related issue?

Yes. CVE-2026-59847 is described as an integrity downgrade involving OpenSSL AES-GCM tag verification. The provided information does not specify affected configurations or exploitation prerequisites.

5

Which packages are included in this advisory?

The advisory lists redhat/libssh, redhat/libssh-debuginfo, redhat/libssh-debugsource, redhat/libssh-devel, and redhat/libssh-config.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203