VulnerabilityPublished 24 Jun 2025Updated 27 Oct 2026

CVE-2025-5318: versions less than

Affects libsshSource GCVE Database

Authoritative record:CVE-2025-5318· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium · fixed in 0.6.3-4.3ubuntu0.6+esm2 : update libssh when convenient.

Data as of 27 Oct 2026, 06:42 UTC

CVSS 3.1 base score

5.4Medium

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

Patch: Available – fixed in 0.6.3-4.3ubuntu0.6+esm2, 0.8.0~20170825.94fa1e38-1ubuntu0.7+esm4, 0.9.3-2ubuntu2.5+esm1 +2

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

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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

Upgrade to a fixed release listed under Affected software.

Patches and advisories

Affected software

Product	Affected	Fixed in
Ubuntu 24.04 LTSlibssh`pkg:deb/ubuntu/libssh?arch=source&distro=noble`Other threats	Affected <0.10.6-2ubuntu0.1	Fixed in 0.10.6-2ubuntu0.1
Ubuntu 22.04 LTSlibssh`pkg:deb/ubuntu/libssh?arch=source&distro=jammy`Other threats	Affected <0.9.6-2ubuntu0.22.04.4	Fixed in 0.9.6-2ubuntu0.22.04.4
Ubuntu Pro 20.04 LTSlibssh`pkg:deb/ubuntu/libssh?arch=source&distro=esm-infra/focal`Other threats	Affected <0.9.3-2ubuntu2.5+esm1	Fixed in 0.9.3-2ubuntu2.5+esm1
Ubuntu Pro 18.04 LTSlibssh`pkg:deb/ubuntu/libssh?arch=source&distro=esm-infra/bionic`Other threats	Affected <0.8.0~20170825.94fa1e38-1ubuntu0.7+esm4	Fixed in 0.8.0~20170825.94fa1e38-1ubuntu0.7+esm4
Ubuntu Pro 16.04 LTSlibssh`pkg:deb/ubuntu/libssh?arch=source&distro=esm-infra/xenial`Other threats	Affected <0.6.3-4.3ubuntu0.6+esm2	Fixed in 0.6.3-4.3ubuntu0.6+esm2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A flaw was found in the libssh library in versions less than 0.11.2. An out-of-bounds read can be triggered in the sftp_handle function due to an incorrect comparison check that permits the function to access memory beyond the valid handle list and to return an invalid pointer, which is used in further processing. This vulnerability allows an authenticated remote attacker to potentially read unintended memory regions, exposing sensitive information or affect service behavior.

References

Community reviews

Loading reviews…