Open-source package vulnerability · Go

GHSA-xhj4-g6w8-2xjw: go-zserio has Unbounded Memory Allocation for All Platforms

criticalCVSS 3.1 9.8

Impact When deserializing arrays, strings or bytes (blob) types zserio first reads the size of the variable, and then allocates sufficient memory to load data. Since the size is always trusted this can be abused by creating a data file with a large size value, causing the zserio runtime to allocate large amounts of memory. Patches Please apply this commit.

Published Apr 24, 2026

Affected packages

github.com/woven-planet/go-zserio

Ecosystem: Go
Affected: < 0.9.1
Fixed in: 0.9.1
Check: go list -m github.com/woven-planet/go-zserio

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

When deserializing arrays, strings or bytes (blob) types zserio first reads the size of the variable, and then allocates sufficient memory to load data. Since the size is always trusted this can be abused by creating a data file with a large size value, causing the zserio runtime to allocate large amounts of memory.

Patches

Please apply this commit.

Workarounds

Do not accept zserio data from non-trusted sources.
Use secure transportation protocols (like TLS).

Credited to Ryujiyasu.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology