Critical OpenSSH Flaws Allow Plaintext Recovery, File Write, and Injection

Key Takeaways

• OpenSSH 10.6, released October 6, 2026, addresses multiple security vulnerabilities across its client and server components.
• Critical flaws include a plaintext recovery risk via shared compression, an arbitrary file write vulnerability in SFTP, and potential shell injection.
• The compression vulnerability (CVE-2026-XXXX) could allow attackers to recover secrets by analyzing encrypted traffic lengths.
• Fixes are available in OpenSSH 10.6; immediate updates are recommended for all users and administrators.

OpenSSH 10.6, launched on October 6, 2026, introduces crucial security patches designed to mitigate vulnerabilities that could lead to data exposure, unauthorized file writes, or shell command injection under specific operational conditions. This significant update affects both the client and server tools, making it essential for all administrators and users who depend on SSH for secure remote access and file transfer operations.

According to the official release notes, the update addresses several distinct weaknesses, each with unique attack prerequisites, rather than a single, universal vulnerability. Primary concerns include how SSH channels handle shared compression, the processing of paths returned by SFTP servers, and the handling of untrusted usernames within shell commands.

SSH Plaintext Recovery Risk

Researchers Fabian Bäumer and Marcus Brinkmann detailed a significant compression flaw in their paper, Crossing the Streams. This vulnerability arises when compression is active, causing all channels within a single SSH connection to share a common compression dictionary. An adversary capable of injecting arbitrary text into one channel and subsequently monitoring the lengths of encrypted traffic can exploit these variations to deduce sensitive information transmitted through another channel.

The core of this leakage lies in the LZ77 compression algorithm, which operates by replacing repetitive text sequences with references to previously encountered data. If attacker-controlled input happens to match a segment of a secret, the resulting changes in traffic length can provide revealing clues. It is important to note that this method does not directly compromise SSH encryption itself but rather exploits information exposed by the compression process before encryption is applied.

In the researchers’ most efficient testing scenario, an eight-character secret derived from a 26-letter alphabet could be recovered with a maximum of 276 guesses. This outcome is highly dependent on the specific conditions under which the test was conducted and should not be interpreted as a universally applicable recovery rate.

OpenSSH 10.6 addresses this issue by disabling the LZ77 dictionary coder in both the ssh client and sshd server. While compression functionality remains, its effectiveness is reduced. The developers advocate for the use of application-level compression whenever feasible, discouraging the practice of sharing SSH compression across both trusted and untrusted traffic streams.

File Write and Injection Flaws

The SFTP component received a fix that enhances the validation of paths returned by a server. Prior to this patch, a malicious SFTP server could manipulate paths, potentially redirecting a recursive copy operation to write files outside of its intended target directory. This vulnerability was identified by researcher Junghoon Cho, who also provided a patch. The risk pertains to how the client processes server responses, not to an unauthenticated attacker writing to any SSH server.

Another critical patch prevents the use of dollar signs and backslashes in destination usernames provided via the SSH command line. In certain configurations, usernames originating from untrusted sources could be processed within shell contexts through features such as ProxyCommand or Match exec, leading to potential command injection. This issue was reported by SecBuddyF KeenLab Tencent. It’s worth noting that usernames configured through the User directive in configuration files are exempt from this new restriction. OpenSSH developers caution that character filtering alone cannot fully safeguard against every shell environment and setup, emphasizing that applications should avoid passing untrusted input directly into SSH command lines.

This news follows previous OpenSSH 10.3 updates that addressed shell injection vulnerabilities, which included enhancements to username and ProxyJump checks. Those earlier fixes are distinct from the protections introduced in the current release.

The OpenSSH 10.6 release also incorporates fixes for GSSAPI credential handling, tunnel restrictions, oversized decompressed packets, and certificate date conversion. For specific older platforms, including QNX 6 and SCO OpenServer 5, the update disables forwarding options that were linked to retained root privileges.

Administrators are strongly advised to review these comprehensive changes during the deployment of the update, particularly in environments where compression or forwarding capabilities are critical. Meanwhile, maintainers anticipate an increase in release frequency due to the rise of AI-assisted vulnerability reports, underscoring the potential for attackers to independently discover similar flaws. Human review, comprehensive test cases, and proposed fixes remain indispensable for validating these reports effectively.

What You Should Do

• Update Immediately: All users and administrators should update to OpenSSH 10.6 without delay to mitigate the identified vulnerabilities.
• Review Configurations: Examine your SSH server and client configurations, paying close attention to compression settings and how usernames are handled, especially if they originate from untrusted sources.
• Limit Compression: If possible, disable or limit shared SSH compression, particularly for connections that handle both trusted and untrusted traffic. Consider using application-level compression instead.
• Validate Input: Ensure that applications do not pass untrusted input directly into SSH command lines to prevent shell injection risks.
• Stay Informed: Regularly monitor the official OpenSSH release notes for further security advisories and updates.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.