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.
CVE-2026-87776
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
September 11, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 11, 2026Security Advisories | OpenJS Foundation CVE Numbering Authority
https://cna.openjsf.org/security-advisories.htmlcompression vulnerable to Denial of Service via memory leak on premature response close · Advisory · expressjs/compression · GitHub
https://github.com/expressjs/compression/security/advisories/GHSA-vc2v-76pw-4v95Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 17× in last 7d / 22× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 11:04 UTCVendor advisory
- 2026-09-18 22:27 UTCEG score recompute
- 2026-09-18 22:27 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 09:50 UTCVendor advisory
- 2026-09-17 21:13 UTCEG score recompute
- 2026-09-17 21:13 UTCVendor advisory
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 08:36 UTCVendor advisory
- 2026-09-16 19:59 UTCEG score recompute
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 08:50 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 06:53 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-13 16:51 UTCEG score recompute
- 2026-09-12 15:37 UTCEG score recompute
- 2026-09-11 14:23 UTCEG score recompute
- 2026-09-11 13:46 UTCEG score recompute
- 2026-09-11 12:22 UTCEG score recompute
- 2026-09-11 11:38 UTCEG score recompute
- 2026-09-11 11:34 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-87776?
When was CVE-2026-87776 disclosed?
Is CVE-2026-87776 actively exploited?
What is the CVSS score of CVE-2026-87776?
How do I remediate CVE-2026-87776?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-87776
Is Your Infrastructure Affected by CVE-2026-87776?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.