go-grpc-compression has a zstd decompression bombing vulnerability
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/mostynb/go-grpc-compression 1.2.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/mostynb/go-grpc-compression
- Affected
- >= 1.1.4, < 1.2.3
- Fixed in
- 1.2.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-87m9-rv8p-rgmg lists affected ranges: Go github.com/mostynb/go-grpc-compression >=1.1.4 <1.2.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Impact A malicious user could cause a denial of service (DoS) when using a specially crafted gRPC request. The decompression mechanism for zstd did not respect the limits imposed by gRPC, allowing rapid memory usage increases. Versions v1.1.4 through to v1.2.2 made use of the Decoder.DecodeAll function in github.com/klauspost/compress/zstd to decompress data provided by the peer. The vulnerability is exploitable only by attackers who can send gRPC payloads to users of github.com/mostynb/go-grpc-compression/zstd or github.com/mostynb/go-grpc-compression/nonclobbering/zstd. Patches Version v1.2.3 of github.com/mostynb/go-grpc-compression avoids the issue by not using the Decoder.DecodeAll function in github.com/klauspost/compress/zstd. All users of github.com/mostynb/go-grpc-compression/zstd or github.com/mostynb/go-grpc-compression/nonclobbering/zstd in the affected versions should update to v1.2.3. Workarounds Other compression formats were not affected, users may consider switching…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-87m9-rv8p-rgmg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-87m9-rv8p-rgmg Advisory: go-grpc-compression has a zstd decompression bombing vulnerability IDs: GHSA-87m9-rv8p-rgmg Record: https://patchnext.com/advisories/ghsa-87m9-rv8p-rgmg (revision 1, source checked 26 Oct 2026, 15:04 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/mostynb/go-grpc-compression 1.2.3. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/mostynb/go-grpc-compression: affected >= 1.1.4, < 1.2.3; fixed in 1.2.3 ## Suggested inspection (read-only) - Go github.com/mostynb/go-grpc-compression: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/mostynb/go-grpc-compression. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-87m9-rv8p-rgmg (GitHub-reviewed advisory GHSA-87m9-rv8p-rgmg lists affected ranges: Go github.com/mostynb/go-grpc-compression >=1.1.4 <1.2.3) Commands are suggestions: review each one before running it.
Loading voting…