Is Snappier 1.1 vulnerable?

NuGet · 7 releases from 1.1.0 to 1.1.6 · latest Snappier is 1.3.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. Snappier 1.1.6, the last 1.1 release, is affected by 1 known security advisory (1 high), including CVE-2026-44302. 1 more affects earlier 1.1.x releases. Upgrade to 1.3.1 or later to fix all of them.

Upgrade with:dotnet add package Snappier --version 1.3.1

Is your project on an affected Snappier?

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

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

Advisories affecting Snappier 1.1.6

  • HighCVE-2026-44302GHSA-pggp-6c3x-2xmx6 May 2026

    Snappier has an infinite loop during SnappyStream decompression with malformed framed input

    Affected
    <1.3.1
    Fixed in
    1.3.1

Fixed within 1.1.x, affecting earlier releases

  • HighCVE-2023-28638GHSA-838x-pcvx-6p5w27 Mar 2023

    Snappier vulnerable to buffer overrun due to improper restriction of operations within the bounds of a memory buffer

    Affected
    >=1.1.0 <1.1.1
    Fixed in
    1.1.1

Every Snappier 1.1.x release

Affected: 1.1.0 to 1.1.6. Latest Snappier: 1.3.2.

VersionKnown advisories
Snappier 1.1.6CVE-2026-44302
Snappier 1.1.5CVE-2026-44302
Snappier 1.1.4CVE-2026-44302
Snappier 1.1.3CVE-2026-44302
Snappier 1.1.2CVE-2026-44302
Snappier 1.1.1CVE-2026-44302
Snappier 1.1.0CVE-2026-44302, CVE-2023-28638

Which of your client projects are still on Snappier 1.1?

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

Other Snappier versions

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