<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Libssh &lt; 0.11.5 - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/libssh--0.11.5/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 21 Jul 2026 15:21:32 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/libssh--0.11.5/feed.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-59851: Libssh GSSAPIKeyExchange Authorization Bypass</title><link>https://feed.craftedsignal.io/briefs/2026-07-cve-2026-59851-libssh-gssapikeyexchange-bypass/</link><pubDate>Tue, 21 Jul 2026 15:21:32 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-cve-2026-59851-libssh-gssapikeyexchange-bypass/</guid><description>A vulnerability in libssh, tracked as CVE-2026-59851, allows an authenticated Kerberos principal to bypass authorization checks on servers with GSSAPIKeyExchange enabled, enabling arbitrary local user login and potential privilege escalation.</description><content:encoded><![CDATA[<p>CVE-2026-59851 describes a critical authorization bypass vulnerability within the libssh library when configured on servers with GSSAPIKeyExchange enabled. This flaw resides specifically in the <code>gssapi-keyex</code> path, where the library fails to properly verify if an already authenticated Kerberos principal is authorized to log in as the requested local user. This allows an attacker, who has successfully authenticated via Kerberos, to potentially assume the identity of any arbitrary local user on the system, including privileged accounts, leading to unauthorized access and privilege escalation. While no specific threat actor or active exploitation campaigns have been detailed in the NVD source, the high CVSS score of 8.8 indicates a severe risk. Defenders should prioritize patching and configuration review to mitigate this risk, as successful exploitation could grant full control over affected systems.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker obtains valid Kerberos credentials for an account within the target network environment.</li>
<li>The attacker initiates an SSH connection to a server running a vulnerable version of libssh with GSSAPIKeyExchange explicitly enabled.</li>
<li>During the SSH authentication process, the attacker leverages their Kerberos credentials via the GSSAPIKeyExchange mechanism.</li>
<li>The vulnerable libssh server's <code>gssapi-keyex</code> path processes the Kerberos authentication request.</li>
<li>Due to the flaw (CVE-2026-59851), the server incorrectly maps the authenticated Kerberos principal to an arbitrary local user specified by the attacker, bypassing proper authorization checks.</li>
<li>The libssh server grants the attacker a session as the chosen arbitrary local user, potentially leading to privilege escalation if a privileged user (e.g., <code>root</code>) is targeted.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-59851 allows an authenticated attacker to bypass intended authorization mechanisms and log in as any local user on the compromised server. This can lead to severe consequences, including unauthorized access to sensitive data, modification or deletion of system files, and complete system compromise, particularly if the attacker gains access as an administrative user. Organizations using libssh with GSSAPIKeyExchange enabled in environments with Kerberos authentication are at risk, and the impact could range from data exfiltration to total disruption of services.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch CVE-2026-59851 by updating all libssh installations to a fixed version immediately.</li>
<li>If immediate patching is not feasible, review system configurations and disable <code>GSSAPIKeyExchange</code> on libssh servers unless absolutely necessary.</li>
<li>Implement robust monitoring of authentication logs for unusual login attempts or successful logins by Kerberos principals mapped to unexpected local user accounts, leveraging available log sources.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>vulnerability</category><category>authorization-bypass</category><category>privilege-escalation</category><category>libssh</category></item></channel></rss>