VulnerabilityPublished 21 Jul 2026Updated 1 Sep 2026

CVE-2026-59844: Excessive Memory Allocation

Source GCVE Database

Compare

Authoritative record:CVE-2026-59844· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

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

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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jul 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.

ghsa-qp28-hpg5-j7xc

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10libssh	Affected–	Fixed in–
Red Hat Enterprise Linux 8libssh	Affected–	Fixed in–
Red Hat Enterprise Linux 8libssh	Affected–	Fixed in–
Red Hat Enterprise Linux 9libssh	Affected–	Fixed in–
Red Hat Enterprise Linux 9libssh	Affected–	Fixed in–
Red Hat Hardened Imageslibssh-main	Affected–	Fixed in–

AI-suggested

Red Hat has released updated libssh packages (libssh-0.12.1-4.hum1 and related) that address this vulnerability. Users should apply these official updates to remediate the issue. No workaround or temporary fix is available, so patching is the only mitigation.

Description

A vulnerability in libssh allows a remote authenticated client to send SSH_FXP_READ requests with an arbitrarily large length, causing the SFTP server to allocate excessive memory. This can lead to memory exhaustion and denial of service through repeated requests. The issue is tracked as CVE-2026-59844 with a CVSS score of 6.5 (medium severity). Red Hat has released an update for libssh to address this flaw. No workaround is available, so applying the vendor's update is the recommended mitigation.

Impact

The vulnerability can be exploited by a remote authenticated client to cause the libssh SFTP server to consume excessive memory, potentially leading to denial of service by exhausting system resources. There is no impact on confidentiality or integrity, but availability is severely affected.

Summary

CVE-2026-59844 describes a flaw in libssh where a remote authenticated client can issue SSH_FXP_READ requests specifying an excessively large length. This causes the libssh SFTP server to allocate excessive memory, potentially exhausting system memory and resulting in a denial of service condition. The vulnerability is classified under CWE-789 (Memory Allocation with Excessive Size Value). Red Hat has published an advisory and released updated libssh packages (version 0.12.1-4.hum1) to fix this issue. No workaround exists, and the vulnerability requires applying the official fix.

CWE-789Memory Allocation with Excessive Size Value (opens in a new tab)
Variant weakness
The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.
Implementation · Architecture and Design
Perform adequate input validation against any value that influences the amount of memory that is allocated. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to be used if necessary.
Operation
Run your program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (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 13 Sep 2026, 20:04 UTC

WeaknessesCWE-789

Technical details

References

Community reviews

Related threats