Skip to main content
CVE-2026-55200VulnerabilityPublished Updated

Microsoft · libssh2 - Out-of-Bounds Write via Unchecked packet_length in transport.c

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-55200· Critical 9.2

Not known to be exploited · CVSS 9.2 Critical : upgrade to 97acf3dfda80c91c3a8c9f2372546301d4a1a7a8 as a priority.

Data as of 17 Nov 2026, 10:20 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.09.2
CNA (VulnCheck)CVSS 3.18.1
Patch
Available – fixed in 97acf3dfda80c91c3a8c9f2372546301d4a1a7a8
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 17 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by VulnCheck

    , 27 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , the same day as disclosure

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

What to do

Upgrade libssh2 to 97acf3dfda80c91c3a8c9f2372546301d4a1a7a8.

Affected software

ProductAffectedFixed in
libssh2libssh2Affected
  • =1.11.1
Fixed in
  • 97acf3dfda80c91c3a8c9f2372546301d4a1a7a8
GitHublibssh2pkg:github/libssh2Other threatsAffected
  • =1.11.1
Fixed in–

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

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…