RHSA-2026:42922HighCVSS 8.8

Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Published
July 21, 2026
Last Modified
September 6, 2026

🔗 CVE IDs covered (10)

CVE-2026-59846 →CVE-2026-59847 →CVE-2026-59849 →CVE-2026-59850 →CVE-2026-59851 →CVE-2026-59843 →CVE-2026-59844 →CVE-2026-59848 →CVE-2026-59842 →CVE-2026-59845 →

📋 Description

CVE-2026-59842 — libssh: libssh: information disclosure via short GSSAPI Curve25519 public key CVE-2026-59843 — libssh: libssh: denial of service via zero advertised channel packet size CVE-2026-59844 — libssh: libssh: denial of service via oversized SFTP read length CVE-2026-59845 — libssh: libssh: denial of service via unchecked ProxyCommand fork() failure CVE-2026-59846 — libssh: libssh: information disclosure via ProxyCommand %r username expansion CVE-2026-59847 — libssh: libssh: integrity downgrade via OpenSSL AES-GCM tag verification CVE-2026-59848 — libssh: libssh: denial of service via SFTP responses with unknown request IDs CVE-2026-59849 — libssh: libssh: denial of service via automatic certificate authentication loop CVE-2026-59850 — libssh: libssh: use-after-free via data callbacks on closed channels CVE-2026-59851 — libssh: libssh: authentication bypass via missing GSSAPI principal check

🎯 Affected products5

  • Red Hat Hardened Images
  • libssh-main@aarch64 as a component of Red Hat Hardened Images
  • libssh-main@noarch as a component of Red Hat Hardened Images
  • libssh-main@src as a component of Red Hat Hardened Images
  • libssh-main@x86_64 as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: Disable GSSAPIKeyExchange or remove gss-curve25519-sha256- from GSSAPIKexAlgorithms if appropriate. Workaround: No workaround available. Workaround: To mitigate this issue, avoid using the ProxyCommand feature in libssh client configurations. This prevents the vulnerable code path from being exercised, thereby eliminating the risk of local denial of service due to unchecked fork() failures. Workaround: Make sure you are not executing connections with untrusted username inputs. Workaround: Disable the [email protected] and [email protected] ciphers. Workaround: Do not connect to untrusted SFTP servers. Workaround: Do not connect to untrusted SSH servers and do not use certificates until patched. Workaround: Manually verify the channel is not closed inside your channel data callbacks. Workaround: Disable GSSAPIKeyExchange.

🔗 References (14)