libssh2 - Out-of-Bounds Write via Unchecked packet_length in transport.c
libssh2 · libssh2
9.2CriticalCVSS 4.0
Recommended action
Within 72 hours
Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Evidence used
No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.83% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
Confirm that the asset runs libssh2 libssh2 and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
Release-specific package status
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
7 package states
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
Distribution release
Source package
Vendor state
Fixed version
Evidence
Alpine v3.23v3.23 · main
libssh2
Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
1 current
CVE-2026-55200 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylibssh2: libssh2 - Out-of-Bounds Write via Unchecked packet_length in transport.c
8 known affected
The vendor explicitly identifies these products as affected by this CVE.
libssh2 as a component of Red Hat Enterprise Linux 6
libssh2-devel as a component of Red Hat Enterprise Linux 6
libssh2-docs as a component of Red Hat Enterprise Linux 6
libssh2.src as a component of Red Hat Enterprise Linux 6
libssh2-devel (virt:rhel) as a component of Red Hat Enterprise Linux 8
libssh2-docs (virt:rhel) as a component of Red Hat Enterprise Linux 8
libssh2.src (virt:rhel) as a component of Red Hat Enterprise Linux 8
libssh2 (virt:rhel) as a component of Red Hat Enterprise Linux 8
Summary
An out-of-bounds write vulnerability exists in the libssh2 client. A remote attacker can exploit this by sending a specially crafted SSH packet with an abnormally large length value. This corrupts the application's memory and can potentially allow the attacker to execute arbitrary code on the affected system.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-37784
No EUVD known-exploited evidence
ENISA has published the identifier mapping but no EUVD description has been stored yet.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours
Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.
Patch available
01
What, why and how
libssh2 through 1.11.1, fixed in commit 7acf3df contains an out-of-bounds write vulnerability in ssh2_transport_read() that fails to enforce upper bounds on packet_length field. Remote attackers can send crafted SSH packets with excessively large packet_length values to corrupt heap memory and achieve remote code execution.
What
libssh2 through 1.11.1, fixed in commit 7acf3df contains an out-of-bounds write vulnerability in ssh2_transport_read() that fails to enforce upper bounds on packet_length field. Remote attackers can send crafted SSH packets with excessively large packet_length values to corrupt heap memory and achieve remote code execution.
Why
The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
libssh2 through 1.11.1, fixed in commit 7acf3df contains an out-of-bounds write vulnerability in ssh2_transport_read() that fails to enforce upper bounds on packet_length field. Remote attackers can send crafted SSH packets with excessively large packet_length values to corrupt heap memory and achieve remote code execution.
Why
The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
Likely attack path
a network path → Integer Overflow to Buffer Overflow → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-680: Integer Overflow to Buffer Overflow. The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in libssh2 ausnutzen, um einen Denial of Service Angriff durchzuführen oder Code auszuführen.
Official advisory ↗Cyber Security Agency of Singapore · English · CSA-SB-20260624Security Bulletin 24 June 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 24 June 2026, published on 24 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
Official advisory ↗CERT-FR · French · CERTFR-2026-AVI-0812Multiples vulnérabilités dans Microsoft Azure Linux
ulletin de sécurité Microsoft CVE-2026-53255 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53263 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53264 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53265 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53266 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53267 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53268 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53270 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53274 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-53275 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-55200 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-9675 du 27 juin 2026
Bulletin de sécurité Microsoft CVE-2026-9697 du 27 juin 2026
Une gestion de version détaillée se trouve à la fin de ce document.
Risque
Non spécifié par l'éditeur
Systèmes affectés
azl3 kernel 6.6.141.1-1 versions antérieures à 6.6.143.1-1
azl3 libssh2 1.11.1-2 versions antérieures à 1.11.1-3
azl3 libssh2 1.11.1-3 versions antérieures à 1.11.1-3
azl3 nodejs 24.14.1-3 versions antérieures à 24.17.0-1
Résumé
De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par
Official advisory ↗NCSC-NL · Dutch · NCSC-2026-0210Kwetsbaarheden verholpen in libssh2 door libssh
libssh2 versions up to 1.11.1 contain an out-of-bounds write vulnerability in ssh2_transport_read() due to improper bounds checking on packet_length, enabling remote attackers to execute arbitrary code via crafted SSH packets.
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 17 Jun 2026 · Last source change 14 Jul 2026, 21:33 UTC · CWE-680 · Integer Overflow to Buffer Overflow
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-37784
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.