cve.bz

CVE-2026-45309 asyncssh project asyncssh: Path traversal

8.2 highExploit referenceEPSS 0.6%Fix available

High (8.2) in asyncssh project asyncssh. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in asyncssh 2.23.0.

On this page
AsyncSSH is a Python package which provides an asynchronous client and server implementation of the SSHv2 protocol on top of the Python asyncio framework. Prior to 2.23.0, AsyncSSH expands the OpenSSH-compatible AuthorizedKeysFile %u token in asyncssh/config.py, asyncssh/connection.py, asyncssh/auth_keys.py, and asyncssh/misc.py with the raw SSH username during pre-authentication server config reload, allowing a server configured with AuthorizedKeysFile authorized_keys/%u to read an authorized-keys file outside the intended directory when the SSH username contains /, \, or .. path traversal segments and authenticate with an attacker-selected key file. This issue is fixed in version 2.23.0.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-07-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-45309 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-45309?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-45309?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-45309 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-45309

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-45309](https://cve.bz/cve/badge/CVE-2026-45309.svg)](https://cve.bz/cve/CVE-2026-45309)

HTML:

<a href="https://cve.bz/cve/CVE-2026-45309"><img src="https://cve.bz/cve/badge/CVE-2026-45309.svg" alt="CVE-2026-45309"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
asyncssh_project:asyncsshbefore 2.23.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-g794-3fmp-753hPyPIasyncssh>=2.22.0 <2.23.02.23.0
PYSEC-2026-2384PyPIasyncssh>=2.22.0 <2.23.02.23.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13python-asyncsshno fix listedDEBIAN-CVE-2026-45309
Debian14python-asyncssh2.23.0-1DEBIAN-CVE-2026-45309
Ubuntu16.04:LTS, 20.04:LTS, 26.04:LTS and 3 morepython-asyncsshno fix listedUBUNTU-CVE-2026-45309
openSUSETumbleweedpython-asyncssh2.23.1-1.1openSUSE-SU-2026:11042-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat rates this vulnerability as Moderate rather than the upstream HIGH severity because exploitation requires the AsyncSSH server to be specifically configured with AuthorizedKeysFile %u, a non-default setting that is not commonly deployed in Red Hat environments. While the flaw allows a remote, unauthenticated attacker to traverse the filesystem path during SSH pre-authentication to reference an unintended authorized_keys file, the practical exploitability is constrained by this prerequisite configuration, and the impact is limited to integrity of the authentication mechanism with no direct confidentiality or availability impact.

ProductPackageStateAdvisory
Red Hat Ceph Storage 7rhceph/rhceph-7-rhel9Fix deferred
Red Hat Ceph Storage 8rhceph/rhceph-8-rhel9Fix deferred
Red Hat Ceph Storage 9rhceph/rhceph-9-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-45309.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON