Skip to main content
CVE-2023-46445VulnerabilityPublished Updated

CVE-2023-46445: asyncssh · n/a

Affects asyncsshSource CVE Database V5

0

Not known to be exploited : upgrade to 2.14.1 when convenient.

Data as of 25 Oct 2026, 22:43 UTC

Severity
Medium

Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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

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 2026-10-25.

What to do

Upgrade asyncssh to 2.14.1.

Affected software

ProductAffectedFixed in
PyPIasyncsshpkg:pypi/asyncsshOther threatsAffected
  • <2.14.1
Fixed in
  • 2.14.1

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

AI-suggested

Users should upgrade AsyncSSH to version 2.14.1 or later, where this vulnerability has been fixed. No other mitigation actions are indicated by the vendor advisory.

Description

AsyncSSH versions prior to 2.14.1 contain a vulnerability that allows an attacker to manipulate the extension info message as defined in RFC 8308 through a man-in-the-middle attack, known as a "Rogue Extension Negotiation." This issue was fixed in version 2.14.1.

References

Community reviews

Loading reviews…