Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-0968 low CVSS 3.1

Vulnerability in Libssh (CVE-2026-0968)

Summary

Vulnerability in Libssh (CVE-2026-0968). Risk of unauthorized operations or information disclosure. Exploitable via SSH_FXP_NAME.

Original description

The description as published by the source.

A flaw was found in libssh in which a malicious SFTP (SSH File Transfer Protocol) server can exploit this by sending a malformed 'longname' field within an SSH_FXP_NAME message during a file listing operation. This missing null check can lead to reading beyond allocated memory on the heap. This can cause unexpected behavior or lead to a denial of service (DoS) due to application crashes.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-0968 has been found in Libssh.
Attackers can target a specific entry point like SSH_FXP_NAME over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Libssh CVE-2026-0968" on the vendor's site.

CVE-2026-0968 (Libssh) — CWE-476 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: SSH_FXP_NAME
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

A vulnerability (CWE-476) exists in Libssh. Attackers reach the vulnerable code path via SSH_FXP_NAME without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Libssh. Attack surface: SSH_FXP_NAME.

🔥 Severity

Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 'Libssh' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Libssh' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Libssh を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details