Skip to content
VulniPulse
Advisory severityMedium4.3Red Hat Linux

Medium [CVE-2026-55653] Double free in Red Hat Enterprise Linux versions of OpenSSH DH-GEX client path during FIPS known-group validation leads to client-side denial of service

This medium-severity Red Hat Linux advisory covers CVE-2026-55653 affecting Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-55653 Source published Source updated

VulniPulse record published Record updated

CVE-2026-55653
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Summary

A flaw was found in OpenSSH. A malicious SSH server can exploit a double free vulnerability in the Diffie-Hellman Group Exchange (DH-GEX) client path.

This occurs during FIPS (Federal Information Processing Standards) mode known-group validation when the client processes attacker-controlled DH-GEX group parameters. Successful exploitation leads to client-side process termination, resulting in a Denial of Service (DoS).

This Moderate flaw in OpenSSH affects clients operating in FIPS mode when negotiating Diffie-Hellman Group Exchange (DH-GEX) with a malicious SSH server. While it can lead to client process termination, resulting in a denial of service, the impact is limited to availability and does not result in broader system compromise.

In order to exploit this vulnerability the attacker needs to trick the user to connect to an untrusted malicious server or compromise the server first. The availability impact is considered Low as the only impacted process is the single run of the SSH client trying to connect to the malicious server.

This vulnerability affects only the OpenSSH versions shipped with Red Hat products. Red Hat severity: Moderate — CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L).

Weakness: CWE-415.

Is CVE-2026-55653 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-55653 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-55653?

Upgrade to a fixed release named by Red Hat:

  • openssh-0:9.9p1-25.el10_2
  • openssh-0:9.9p1-7.el10_0.5
  • openssh-0:8.0p1-30.el8_10
  • openssh-0:9.9p1-9.el9_8
  • openssh-0:8.7p1-38.el9_4.10
  • openssh-0:8.7p1-45.el9_6.5
  • openssh-main-10.3p1-6.hum1
  • rhai/base-image-cuda-rhel9:1791818590
  • rhai/base-image-cpu-rhel9:1791818589
  • rhai/base-image-spyre-rhel9:1791818505
  • rhai/base-image-tpu-rhel9:1791818496
  • rhai/base-image-rocm-rhel9:1791818502

38 more fixed releases are listed below.

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Fixed versions
  • openssh-0:9.9p1-25.el10_2
  • openssh-0:9.9p1-7.el10_0.5
  • openssh-0:8.0p1-30.el8_10
  • openssh-0:9.9p1-9.el9_8
  • openssh-0:8.7p1-38.el9_4.10
  • openssh-0:8.7p1-45.el9_6.5
  • openssh-main-10.3p1-6.hum1
  • rhai/base-image-cuda-rhel9:1791818590
  • rhai/base-image-cpu-rhel9:1791818589
  • rhai/base-image-spyre-rhel9:1791818505
  • rhai/base-image-tpu-rhel9:1791818496
  • rhai/base-image-rocm-rhel9:1791818502
  • rhai/base-image-spyre-rhel9:1791818602
  • rhai/base-image-cpu-rhel9:1791818598
  • rhai/base-image-tpu-rhel9:1791818512
  • rhai/base-image-cuda-rhel9:1791818587
  • rhai/base-image-rocm-rhel9:1791818778
  • rhai/base-image-rocm-rhel9:1791818512
  • rhai/base-image-tpu-rhel9:1791818782
  • rhai/base-image-rocm-6.4-rhel9:1791818782
  • rhai/base-image-cuda-12.9-rhel9:1791818627
  • rhai/base-image-rocm-7.0-rhel9:1791818790
  • rhai/base-image-cpu-rhel9:1791818874
  • rhai/base-image-neuron-rhel9:1791818792
  • rhai/base-image-cuda-13.0-rhel9:1791818662
  • rhai/base-image-spyre-rhel9:1791818877
  • rhai/base-image-neuron-rhel9:1791883722
  • rhai/base-image-cuda-12.9-rhel9:1791881612
  • rhai/base-image-cpu-rhel9:1791885618
  • rhai/base-image-rocm-6.4-rhel9:1791881487
  • rhai/base-image-spyre-rhel9:1791881732
  • rhai/base-image-rocm-7.1-rhel9:1791883315
  • rhai/base-image-gaudi-rhel9:1791881486
  • rhai/base-image-tpu-rhel9:1791881769
  • rhai/base-image-cuda-13.0-rhel9:1791885505
  • rhai/base-image-spyre-rhel9:1791819252
  • rhai/base-image-gaudi-rhel9:1791818749
  • rhai/base-image-cpu-rhel9:1791819206
  • rhai/base-image-neuron-rhel9:1791818979
  • rhai/base-image-rocm-7.14-rhel9:1791819123
  • RHSA-2026:47757
  • RHSA-2026:76748
  • RHSA-2026:47755
  • RHSA-2026:47756
  • RHSA-2026:76993
  • RHSA-2026:80513
  • RHSA-2026:36759
  • RHSA-2026:82751
  • RHSA-2026:82761
  • RHSA-2026:82903

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, OpenSSH clients operating in FIPS mode should avoid negotiating the `diffie-hellman-group-exchange-sha256` key exchange algorithm. This can be achieved by explicitly listing allowed key exchange algorithms in the client's SSH configuration file (e.g., `/etc/ssh/ssh_config` or `~/.ssh/config`), ensuring `diffie-hellman-group-exchange-sha256` is *not* included. For example, to use a subset of common algorithms, you might configure: ``` KexAlgorithms [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1 ``` (Note: The above example `KexAlgorithms` list is illustrative and should be adjusted based on your environment's security requirements.) Additionally, avoid using non-fatal client flows, such as `ssh-keyscan`, against untrusted SSH servers while FIPS mode is enabled. Changes to `ssh_config` will take effect for new SSH connections.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Get an email when Red Hat RHEL & SELinux publishes the next one.

See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat RHEL & SELinux
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.