CVE-2026-87776

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-05. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-76072 (ENISA EUVD) · GHSA-vc2v-76pw-4v95 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
Patch available. Sources: github.
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
GitHub advisoryMentions a patch (unverified)

compression 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-4v95

Patch Availability(15)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-compression1.7.4-3, 1.8.1-1, 1.8.2+~1.8.1-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-compression1.7.4-3, 1.8.1-1, 1.8.2+~1.8.1-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-compression1.7.4-3, 1.8.1-1
  • every version up to 1.8.2+~1.8.1-1: fixed in 1.8.2+~1.8.1-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
compression—
  • every version up to 1.8.2: fixed in 1.8.2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 158 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 58 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-11-11 08:01 UTCEchelonGraph re-scored
  4. 2026-11-11 08:01 UTCVendor advisory
  5. 2026-11-11 08:01 UTCGHSA enrichmentGHSA-vc2v-76pw-4v95 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-11-04 23:30 UTCEchelonGraph re-scored
  13. 2026-11-04 23:30 UTCVendor advisory
  14. 2026-11-04 23:30 UTCGHSA enrichmentGHSA-vc2v-76pw-4v95 · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-11-02 20:58 UTCEchelonGraph re-scored
  18. 2026-11-02 20:58 UTCVendor advisory
  19. 2026-11-02 20:58 UTCGHSA enrichmentGHSA-vc2v-76pw-4v95 · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-11-01 07:37 UTCEchelonGraph re-scored
  23. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-vc2v-76pw-4v95 · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
Show 75 more
  1. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-27 12:27 UTCEchelonGraph re-scored
  5. 2026-10-27 12:27 UTCVendor advisory
  6. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-25 13:53 UTCEchelonGraph re-scored
  9. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-19 13:57 UTCEchelonGraph re-scored
  16. 2026-10-19 13:57 UTCVendor advisory
  17. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-18 03:04 UTCEchelonGraph re-scored
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-10-13 05:06 UTCEchelonGraph re-scored
  25. 2026-10-13 05:06 UTCVendor advisory
  26. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  27. 2026-10-12 14:49 UTCEchelonGraph re-scored
  28. 2026-10-11 22:45 UTCVendor advisory
  29. 2026-10-11 19:16 UTCEchelonGraph re-scored
  30. 2026-10-11 16:33 UTCEchelonGraph re-scored
  31. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  32. 2026-10-11 13:49 UTCEchelonGraph re-scored
  33. 2026-10-11 10:03 UTCVendor advisory
  34. 2026-10-10 20:48 UTCEchelonGraph re-scored
  35. 2026-10-10 20:48 UTCVendor advisory
  36. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  37. 2026-10-10 08:11 UTCEchelonGraph re-scored
  38. 2026-10-10 08:11 UTCVendor advisory
  39. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  40. 2026-10-09 19:32 UTCVendor advisory
  41. 2026-10-08 23:35 UTCEchelonGraph re-scored
  42. 2026-10-08 23:35 UTCVendor advisory
  43. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  44. 2026-10-08 08:27 UTCEchelonGraph re-scored
  45. 2026-10-08 08:27 UTCVendor advisory
  46. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  47. 2026-10-07 19:49 UTCVendor advisory
  48. 2026-10-07 03:15 UTCEchelonGraph re-scored
  49. 2026-10-07 03:15 UTCVendor advisory
  50. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  51. 2026-10-06 14:38 UTCVendor advisory
  52. 2026-10-06 02:01 UTCEchelonGraph re-scored
  53. 2026-10-06 02:01 UTCVendor advisory
  54. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  55. 2026-10-05 13:23 UTCVendor advisory
  56. 2026-10-05 00:31 UTCEchelonGraph re-scored
  57. 2026-10-05 00:31 UTCVendor advisory
  58. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  59. 2026-10-04 11:31 UTCVendor advisory
  60. 2026-10-03 22:54 UTCEchelonGraph re-scored
  61. 2026-10-03 22:54 UTCVendor advisory
  62. 2026-10-03 10:17 UTCVendor advisory
  63. 2026-10-02 20:49 UTCEchelonGraph re-scored
  64. 2026-10-02 20:49 UTCVendor advisory
  65. 2026-10-02 07:50 UTCEchelonGraph re-scored
  66. 2026-10-02 07:50 UTCVendor advisory
  67. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  68. 2026-10-01 19:08 UTCVendor advisory
  69. 2026-10-01 05:55 UTCVendor advisory
  70. 2026-09-30 17:18 UTCEchelonGraph re-scored
  71. 2026-09-30 17:18 UTCVendor advisory
  72. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  73. 2026-09-30 02:52 UTCEchelonGraph re-scored
  74. 2026-09-30 02:52 UTCVendor advisory
  75. 2026-09-29 14:15 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-87776?
CVE-2026-87776 is a high-severity vulnerability; its CVE record was published on September 11, 2026. 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…
When was the CVE record for CVE-2026-87776 published?
The CVE record for CVE-2026-87776 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-87776 actively exploited?
CVE-2026-87776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87776?
CVE-2026-87776 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87776?
A fix for CVE-2026-87776 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87776 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-87776

Explore →

Is Your Infrastructure Affected by CVE-2026-87776?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.