CVE-2026-55653VulnerabilityPublished 14 Oct 2026Updated 29 Oct 2026

Red Hat Security Advisory: Red Hat AI Base Images 3.2.5 (TPU)

Affects Red HatSource GCVE Database

Compare

Authoritative record:CVE-2026-55653· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 29 Oct 2026, 07:56 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	4.3

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10openssh	Affected–	Fixed in–
Red Hat Enterprise Linux 10.0 Extended Update Supportopenssh	Affected–	Fixed in–
Red Hat Enterprise Linux 8openssh	Affected–	Fixed in–
Red Hat Enterprise Linux 9openssh	Affected–	Fixed in–
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutionsopenssh	Affected–	Fixed in–
Red Hat Enterprise Linux 9.4 Update Services for SAP Solutionsopenssh	Affected–	Fixed in–

AI-suggested

Red Hat recommends that OpenSSH clients operating in FIPS mode avoid negotiating the 'diffie-hellman-group-exchange-sha256' key exchange algorithm by explicitly configuring allowed algorithms in the SSH client configuration files (e.g., /etc/ssh/ssh_config or ~/.ssh/config). For example, set 'KexAlgorithms' to a list excluding 'diffie-hellman-group-exchange-sha256'. Additionally, avoid using client flows like 'ssh-keyscan' against untrusted SSH servers while FIPS mode is enabled.

Description

A double free vulnerability exists in the OpenSSH client used in Red Hat products when operating in FIPS mode during Diffie-Hellman Group Exchange (DH-GEX) key exchange. A malicious SSH server can exploit this flaw to cause the client process to terminate, resulting in a denial of service (DoS). The impact is limited to availability of the SSH client process and does not lead to broader system compromise. Mitigation involves avoiding the use of the vulnerable key exchange algorithm by configuring the SSH client to exclude 'diffie-hellman-group-exchange-sha256'. No fix has been released yet for this issue in Red Hat AI Base Images 3.2.5 (TPU).

Impact

Successful exploitation causes termination of the SSH client process, resulting in a denial of service limited to the availability of the single SSH client session. There is no impact on confidentiality or integrity, and no broader system compromise is possible. The attacker must control or impersonate the SSH server and trick the user into connecting. The overall availability impact is considered low.

Summary

CVE-2026-55653 is a double free vulnerability in the OpenSSH client shipped with Red Hat products, specifically affecting clients operating in FIPS mode when negotiating Diffie-Hellman Group Exchange (DH-GEX) with a malicious SSH server. The flaw occurs during known-group validation of attacker-controlled DH-GEX parameters, leading to client process termination (denial of service). Exploitation requires the user to connect to a malicious or compromised SSH server. The vulnerability affects only the OpenSSH versions shipped with Red Hat products and does not result in confidentiality or integrity loss. Red Hat advises mitigating this issue by disabling the 'diffie-hellman-group-exchange-sha256' key exchange algorithm in the SSH client configuration.

CWE-415Double Free (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The product calls free() twice on the same memory address.
Architecture and Design
Choose a language that provides automatic memory management.
Implementation
Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly.
Implementation
Use a static analysis tool to find double free instances.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-923Improper Restriction of Communication Channel to Intended Endpoints (opens in a new tab)
Class weakness
The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
Attack patterns
Contradictory Destinations in Traffic Routing Schemes (opens in a new tab)
Android Activity Hijack (opens in a new tab)
DHCP Spoofing (opens in a new tab)
Infrastructure Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-22Improper Limitation of a Pathname to a Restricted Directory (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-358Improperly Implemented Security Check for Standard (opens in a new tab)
Base weakness
The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.
CWE-307Improper Restriction of Excessive Authentication Attempts (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.
Architecture and Design
Common protection mechanisms include: Disconnecting the user after a small number of failed attempts; Implementing a timeout; Locking out a targeted account; Requiring a computational task on the user's part.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authentication (opens in a new tab)
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP ASVS 4.0.3
V2.2.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Dictionary-based Password Attack (opens in a new tab)
Password Brute Forcing (opens in a new tab)
Password Spraying (opens in a new tab)
Credential Stuffing (opens in a new tab)
Use of Known Kerberos Credentials (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 07:56 UTC

WeaknessesCWE-415, CWE-923, CWE-22 +2

Technical details

References

Community reviews

Related threats