# CVE-2026-110927: OpenSSH decompression memory exhaustion

Source: https://junglewise.ai/threats/cve-2026-110927-a-flaw-was-found-in-openssh-after-compression-is-negotiated-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-15. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-110927 · Severity: medium · CVSS 4.3 · Published 2026-10-15

OpenSSH, widely used for secure remote access and file transfer, contains a flaw in its compression handling. After compression is negotiated between client and server, a malicious compressed packet can expand beyond the maximum allowed size, causing the SSH process to consume excessive memory. An attacker with network access could trigger this to degrade service availability or exhaust system resources.

Technologies: [OpenSSH](https://junglewise.ai/threats/technologies/openssh-openssh). Vendors: [OpenSSH](https://junglewise.ai/threats/vendors/openssh).

## Quick answers

**Is CVE-2026-110927 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-110927 being exploited in the wild.

**How severe is CVE-2026-110927?** Medium severity, with a CVSS score of 4.3, published 15 October 2026.

**Which products and versions are affected?** OpenSSH OpenSSH.

**Is there a fix for CVE-2026-110927?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-110927 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-110927?** Check whether you run OpenSSH. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in the inflate loop used during payload decompression in OpenSSH. When compression is negotiated during the SSH handshake, the decompression routine fails to enforce the maximum packet size limit, allowing a specially crafted compressed payload to expand indefinitely. This results in unbounded memory allocation in the process handling the SSH connection, achievable by any unauthenticated attacker with network access.

## Affected products

- OpenSSH OpenSSH

## Timeline

- 2026-10-15: disclosed

## References

- [https://catalog.redhat.com/software/containers/](https://catalog.redhat.com/software/containers/)
- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)

## Related threats

- [OpenSSH password authentication bypass on musl libc without PAM](https://junglewise.ai/threats/cve-2026-123158-sshd-in-openssh-before-10-6p2-on-linux-when-musl-libc-is-used)
- [OpenSSH GSSAPI credential persistence authentication bypass](https://junglewise.ai/threats/cve-2026-110924-a-flaw-was-found-in-openssh-with-gssapi-authentication-enabled-a)
- [OpenSSH compression dictionary information disclosure](https://junglewise.ai/threats/cve-2026-110926-a-flaw-was-found-in-openssh-when-compression-is-negotiated)
- [OpenSSH shell metacharacter injection in ProxyCommand](https://junglewise.ai/threats/cve-2026-110925-a-flaw-was-found-in-openssh-a-username-entered-on-the-ssh)
- [OpenSSH path traversal in sftp copy](https://junglewise.ai/threats/cve-2026-110923-a-flaw-was-found-in-openssh-during-an-sftp-copy-a-malicious)