CVE-2026-27820

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 56% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

zlib is a Ruby interface for the zlib compression/decompression library. Versions 3.0.0 and below, 3.1.0, 3.1.1, 3.2.0 and 3.2.1 contain a buffer overflow vulnerability in the Zlib::GzipReader. The zstream_buffer_ungets function prepends caller-provided bytes ahead of previously produced output but fails to guarantee the backing Ruby string has enough capacity before the memmove shifts the existing data. This can lead to memory corruption when the buffer length exceeds capacity. This issue has been fixed in versions 3.0.1, 3.1.2 and 3.2.3.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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 computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

April 16, 2026

Last Modified

May 21, 2026

Advisory Details (1)

Auto-updated Sep 2, 2026
Patch available. Sources: github.
github Patch Available

Buffer Overflow vulnerability in Zlib::GzipReader · Advisory · ruby/zlib · GitHub

https://github.com/ruby/zlib/security/advisories/GHSA-g857-hhfv-j68w

Vendor Advisories for CVE-2026-27820(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatruby4-0-main-4.0.0-33.3.hum12026-04-17redhat
redhatruby3-3-main-3.3.10-23.1.hum12026-04-09redhat
redhatruby3-4-main-3.4.8-31.1.hum12026-04-09redhat

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

(7 across 7 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
ruby—3.4.9-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
ruby—3.4.9-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby2.72.7.4-1 ... 2.7.4-1+deb11u5 (6 versions)2.7.4-1+deb11u6—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby3.13.1.2-7 ... 3.1.2-8.5 (8 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby3.33.3.8-2, 3.3.8-2.1, 3.3.8-2.2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby3.33.3.8-2, 3.3.8-2.1, 3.3.8-2.2——
RubyGems(1)
PackageVulnerable rangeFixed inDependents
zlib0.0.1 ... 3.0.0 (8 versions)3.0.1—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 73× 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.

Showing the most recent 100 of 253 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 15:01 UTCOSV refresh
  3. 2026-09-02 14:11 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-09-01 04:39 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:48 UTCEPSS rescore
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 10:23 UTCVendor advisory
  21. 2026-08-16 06:34 UTCEG score recompute
  22. 2026-08-16 06:34 UTCVendor advisory
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 23:46 UTCVendor advisory
Show 75 more
  1. 2026-08-14 19:57 UTCVendor advisory
  2. 2026-08-14 16:08 UTCVendor advisory
  3. 2026-08-14 12:19 UTCVendor advisory
  4. 2026-08-14 08:29 UTCVendor advisory
  5. 2026-08-14 04:40 UTCEG score recompute
  6. 2026-08-14 04:40 UTCVendor advisory
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 08:54 UTCVendor advisory
  9. 2026-08-13 02:28 UTCVendor advisory
  10. 2026-08-12 22:39 UTCVendor advisory
  11. 2026-08-12 18:50 UTCEG score recompute
  12. 2026-08-12 18:50 UTCVendor advisory
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-12 00:37 UTCVendor advisory
  15. 2026-08-11 20:48 UTCVendor advisory
  16. 2026-08-11 17:00 UTCEG score recompute
  17. 2026-08-11 17:00 UTCVendor advisory
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-11 06:26 UTCVendor advisory
  20. 2026-08-11 02:36 UTCEG score recompute
  21. 2026-08-11 02:36 UTCVendor advisory
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 11:53 UTCVendor advisory
  24. 2026-08-10 07:50 UTCVendor advisory
  25. 2026-08-10 04:02 UTCVendor advisory
  26. 2026-08-10 00:12 UTCVendor advisory
  27. 2026-08-09 20:23 UTCVendor advisory
  28. 2026-08-09 16:34 UTCEG score recompute
  29. 2026-08-09 16:34 UTCVendor advisory
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 12:45 UTCVendor advisory
  32. 2026-08-09 07:46 UTCVendor advisory
  33. 2026-08-09 03:57 UTCEG score recompute
  34. 2026-08-09 03:57 UTCVendor advisory
  35. 2026-08-08 16:37 UTCEPSS rescore
  36. 2026-08-08 08:28 UTCVendor advisory
  37. 2026-08-08 04:39 UTCVendor advisory
  38. 2026-08-08 00:50 UTCVendor advisory
  39. 2026-08-07 21:01 UTCVendor advisory
  40. 2026-08-07 17:12 UTCEG score recompute
  41. 2026-08-07 17:12 UTCVendor advisory
  42. 2026-08-07 13:22 UTCVendor advisory
  43. 2026-08-06 21:30 UTCVendor advisory
  44. 2026-08-06 17:28 UTCEG score recompute
  45. 2026-08-06 17:28 UTCVendor advisory
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-06 12:03 UTCVendor advisory
  48. 2026-08-06 06:58 UTCVendor advisory
  49. 2026-08-06 03:09 UTCVendor advisory
  50. 2026-08-05 23:20 UTCEG score recompute
  51. 2026-08-05 23:20 UTCVendor advisory
  52. 2026-08-05 19:17 UTCEPSS rescore
  53. 2026-08-04 15:10 UTCEPSS rescore
  54. 2026-08-04 05:38 UTCVendor advisory
  55. 2026-08-04 01:22 UTCVendor advisory
  56. 2026-08-03 21:33 UTCEG score recompute
  57. 2026-08-03 21:33 UTCVendor advisory
  58. 2026-08-03 10:36 UTCEPSS rescore
  59. 2026-08-03 00:45 UTCVendor advisory
  60. 2026-08-02 20:49 UTCVendor advisory
  61. 2026-08-02 16:59 UTCVendor advisory
  62. 2026-08-02 13:10 UTCEG score recompute
  63. 2026-08-02 13:10 UTCVendor advisory
  64. 2026-08-02 02:26 UTCEPSS rescore
  65. 2026-08-01 04:16 UTCEPSS rescore
  66. 2026-07-30 16:27 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-28 15:36 UTCEPSS rescore
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-25 14:18 UTCEPSS rescore
  72. 2026-07-25 14:17 UTCEPSS rescore
  73. 2026-07-24 14:17 UTCEPSS rescore
  74. 2026-07-23 14:18 UTCEPSS rescore
  75. 2026-07-23 14:18 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-27820?
CVE-2026-27820 is a critical vulnerability published on April 16, 2026. zlib is a Ruby interface for the zlib compression/decompression library. Versions 3.0.0 and below, 3.1.0, 3.1.1, 3.2.0 and 3.2.1 contain a buffer overflow vulnerability in the Zlib::GzipReader. The zstreambufferungets function prepends caller-provided bytes ahead of previously produced output but…
When was CVE-2026-27820 disclosed?
CVE-2026-27820 was first published in the National Vulnerability Database on April 16, 2026, with the most recent update on May 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27820 actively exploited?
CVE-2026-27820 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.5% of all scored CVEs.
What is the CVSS score of CVE-2026-27820?
CVE-2026-27820 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-27820?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27820, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-27820?

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

Start Free Scan →Browse All CVEs