OpenSSH 10.6 Quietly Rewrites the Rules for SSH Privacy

SSH is supposed to be the safe path for remote admin, file transfer, and tunnelled access. OpenSSH 10.6 shows how fragile that promise can become when multiple logical streams share one encrypted session. The update is built around a privacy fix: it reduces a plaintext-recovery risk tied to shared compression state across multiplexed SSH channels, a design choice that can leak information through ciphertext length even when encryption itself remains intact.

Fast Facts

• OpenSSH 10.6 was released on 2026-10-06.
• The release addresses a plaintext recovery risk in SSH compression handling.
• The described issue involves shared compression state across multiplexed SSH channels.
• The mitigation reduces compression efficiency to limit side-channel leakage.
• The release also includes additional compatibility and hardening changes.

How a secure tunnel can still leak secrets

The key detail is SSH multiplexing. One encrypted connection can carry several logical channels at once, such as shells, forwarding, and file transfer. If compression is shared across those channels, bytes from one stream can influence how another stream is compressed. That creates a side channel: an attacker who can inject chosen data into one channel may be able to learn something about secret data in another by observing changes in compressed length.

This is not a break of SSH encryption. It is a confidentiality problem in the layer around encryption. From a defensive perspective, that distinction matters. Teams often treat “encrypted” as equivalent to “safe,” but transport features like compression, channel sharing, and forwarding can still create measurable leakage paths.

Why the fix matters operationally

OpenSSH 10.6 responds by disabling the compression mechanism implicated in the leak, which is a classic security tradeoff: less efficiency in exchange for less exposure. That may have a small performance cost in some environments, especially where compression was used to save bandwidth on slower links. But the broader lesson is more important than the throughput hit - when secret-bearing and attacker-influenced traffic share state, protocol convenience can become an attack surface.

The release also reflects a broader hardening trend. In addition to the compression change, the update includes compatibility adjustments and other security-oriented fixes in adjacent areas such as file transfer behavior, authentication state handling, and forwarding controls. At the time of writing, public information supports the mitigation and the described side-channel mechanism, but not a fully documented end-to-end root cause beyond that.

Conclusion

OpenSSH 10.6 is a reminder that trust in secure systems has to include the plumbing, not just the cipher. The lesson for operators is simple: review where compression is still enabled, limit mixed-trust SSH workflows, and treat multiplexing as a design choice with security consequences. In modern protocol security, the hidden path is often the one that matters most.

WIKICROOK

• Multiplexed SSH channels: Multiple logical data streams carried over one SSH connection.
• Compression side channel: A leak that infers secrets from changes in compressed data size.
• LZ77 dictionary coder: A compression mechanism used by OpenSSH’s compression path and disabled in 10.6 to reduce side-channel risk.
• Plaintext recovery attack: An attack that tries to reconstruct secret text from indirect leakage rather than by breaking encryption directly.
• Forwarding controls: SSH settings that govern whether tunnels and relayed connections are permitted.