← Back
CVE-2026-48798
high
CVSS 7.1
Path Traversal in SSH.NET (CVE-2026-48798)
Summary
path traversal in SSH.NET (CVE-2026-48798). Data can be tampered with by attackers. Exploitable via ``ScpException``. Mitigation: upgrade to `2026.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48798** has been found in SSH.NET.
Attackers can target a specific entry point like ``ScpException`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade SSH.NET to **2026.0.0** or later.
If unsure, ask your IT team or search "SSH.NET CVE-2026-48798" on the vendor's site.
CVE-2026-48798 (SSH.NET) — CWE-22 / CVSS v3 7.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `ScpException`
Patched: `2026.0.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 SSH.NET. Attackers reach the vulnerable code path via ``ScpException`` without authentication.
📍 Affected scope
SSH.NET — . Attack surface: `ScpException`.
🔥 Severity
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2026.0.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 'SSH.NET' .` 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 'SSH.NET' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `SSH.NET` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade SSH.NET to 2026.0.0ステージング環境で 2026.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
SSH.NET
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.0.0"}]}]
References
- web https://github.com/sshnet/SSH.NET/security/advisories/GHSA-q939-rpr3-3284
- web https://github.com/sshnet/SSH.NET/commit/600be0de543765995a189b5d7cd4efac5007f3ce
- web https://github.com/advisories/GHSA-q939-rpr3-3284
- web https://github.com/sshnet/SSH.NET/releases/tag/2026.0.0
- web https://nvd.nist.gov/vuln/detail/CVE-2026-48798