Is zlib 3.1 vulnerable?

RubyGems · 3 releases from 3.1.0 to 3.1.2 · latest zlib is 3.2.4 · checked 18 Nov 2026

No known advisories in the last release

zlib 3.1.2, the last 3.1 release, has no known advisories. 1 advisory affects earlier 3.1.x releases, so update to 3.1.2.

Update within 3.1:bundle update --conservative zlib # Gemfile: '>= 3.1.2'

Is your project on an affected zlib?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 3.1.x, affecting earlier releases

  • MediumCVE-2026-27820GHSA-g857-hhfv-j68w16 Apr 2026

    Buffer Overflow in Zlib::GzipReader ungetc via large input leads to memory corruption

    Affected
    >=3.2.0 <3.2.3 · >=3.1.0 <3.1.2 · <3.0.1
    Fixed in
    3.0.1, 3.1.2, 3.2.3

Every zlib 3.1.x release

Affected: 3.1.0 to 3.1.1. 3.1.2 is not affected. Latest zlib: 3.2.4.

VersionKnown advisories
zlib 3.1.2None
zlib 3.1.1CVE-2026-27820
zlib 3.1.0CVE-2026-27820

Which of your client projects are still on zlib 3.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact zlib version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other zlib versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.