📦 **Component**: **libssh** library. 🌍 **Affected**: Systems using libssh with `ProxyCommand` enabled. 📅 **Published**: 2026-07-21. ⚠️ *Note: Specific versions not listed in data, assume all vulnerable versions.*
Q4黑客能干啥?(权限/数据)
🕵️ **Hackers' Power**: Local attackers only. 🔒 **Privileges**: Requires **Local** access & **Low** privileges (PR:L). 📉 **Impact**: **High** Availability impact (A:H). ❌ No data theft (C:N, I:N).…
⚖️ **Threshold**: **High** (AC:H). 🔑 **Auth**: Requires **Local** access (AV:L). 👤 **User Interaction**: Required (UI:R). 🚧 **Difficulty**: Hard to exploit remotely; needs local foothold & specific config.
Q6有现成Exp吗?(PoC/在野利用)
🚫 **Public Exploit**: **No**. 📄 **PoCs**: Empty list in data. 🌐 **Wild Exploitation**: None reported. 🛡️ **Status**: Theoretical/Local only.
Q7怎么自查?(特征/扫描)
🔍 **Self-Check**: 1. Scan for **libssh** usage. 2. Check config for **ProxyCommand** directives. 3. Monitor for unexpected process crashes/signals. 📝 **Log Analysis**: Look for fork errors in SSH logs.
Q8官方修了吗?(补丁/缓解)
🛡️ **Official Fix**: **Yes**. 📢 **Source**: Red Hat Security Advisory (RHBZ#2498178). 🔄 **Action**: Update libssh to patched version. 🔗 **Ref**: https://access.redhat.com/security/cve/CVE-2026-59845
Q9没补丁咋办?(临时规避)
🚧 **No Patch Workaround**: 1. **Disable ProxyCommand** if not needed. 2. Restrict local SSH access. 3. Monitor system stability. 🛑 **Mitigation**: Limit user privileges to reduce impact.
Q10急不急?(优先级建议)
⏱️ **Urgency**: **Medium-High** for local admins. 📊 **Priority**: Fix ASAP if `ProxyCommand` is used. 📉 **Risk**: Low for remote, High for local stability. 🎯 **Focus**: Patch libssh immediately.