← Back
CVE-2026-45309
high
CVSS 7.5
Path Traversal in asyncssh (CVE-2026-45309)
Summary
path traversal in asyncssh (CVE-2026-45309). Data can be tampered with by attackers. Exploitable via ``AuthorizedKeysFile``. Mitigation: upgrade to `2.23.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45309** has been found in asyncssh.
Attackers can target a specific entry point like ``AuthorizedKeysFile`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade asyncssh to **2.23.0** or later.
If unsure, ask your IT team or search "asyncssh CVE-2026-45309" on the vendor's site.
CVE-2026-45309 (asyncssh) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `AuthorizedKeysFile` / `af5a81e669633d83d535163f93b6bf3f957c9238` / `sshd_config` / `victim`
Patched: `2.23.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in asyncssh. Attackers reach the vulnerable code path via ``AuthorizedKeysFile`` without authentication.
📍 Affected scope
asyncssh — . Attack surface: `AuthorizedKeysFile` / `af5a81e669633d83d535163f93b6bf3f957c9238` / `sshd_config` / `victim`.
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2.23.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'asyncssh' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'asyncssh' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `asyncssh` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade asyncssh to 2.23.0ステージング環境で 2.23.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
asyncssh
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.23.0"}]}]
PyPI
asyncssh
[{"type":"ECOSYSTEM","events":[{"introduced":"2.22.0"},{"fixed":"2.23.0"}]}]