CVE Vulnerabilities

CVE-2026-87776

Missing Release of Memory after Effective Lifetime

Published: Sep 11, 2026 | Modified: Sep 16, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

compression is a Node.js and Express compression middleware. In versions before 1.8.2, when a client aborts the connection while a compressed response is still being sent, the zlib stream created to compress that response is never destroyed, so each aborted compressed response leaks its native zlib memory. A remote unauthenticated attacker can repeatedly open requests and disconnect early, exhausting the available memory and crashing the server. All applications using compression are affected. The issue is fixed in compression 1.8.2, and users should upgrade to 1.8.2 or later.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Software

NameVendorStart VersionEnd Version
Red Hat Ansible Automation Platform 2.1RedHatansible-automation-platform/automation-portal:1790254963*
Red Hat Ansible Automation Platform 2.2RedHatansible-automation-platform/automation-portal:1790256405*
Red Hat Developer Hub 1.10RedHatrhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend:1791242697*
Red Hat Developer Hub 1.10RedHatrhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:1791251282*
Red Hat Discovery 2RedHatdiscovery/discovery-ui-rhel9:1789677459*
Node-compressionUbuntuupstream*

Potential Mitigations

  • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
  • For example, glibc in Linux provides protection against free of invalid pointers.
  • When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
  • To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References