Advisory record · GHSA-xhj4-g6w8-2xjw

go-zserio has Unbounded Memory Allocation for All Platforms

CVSS 9.8 CriticalCritical

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 24 Apr 2026, 16:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/woven-planet/go-zserioGo<0.9.10.9.1
Identifiers
GHSA-xhj4-g6w8-2xjw · GO-2026-5759
Weakness (CWE)
CWE-789
Published
24 Apr 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The go-zserio package for Go is vulnerable in versions before 0.9.1. When deserializing arrays, strings or blobs, it trusts a size value read from the data and allocates memory for it, so an attacker who can supply a crafted data file can force the runtime to allocate large amounts of memory. Upgrade to version 0.9.1 or later. Until then, do not accept zserio data from untrusted sources.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:06 UTC First seen by agentprime
  2. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.