GHSA-xhj4-g6w8-2xjw
go-zserio has Unbounded Memory Allocation for All Platforms
GHSA-xhj4-g6w8-2xjw is a critical vulnerability (CVSS 9.8) in github.com/woven-planet/go-zserio, published April 24, 2026. No source lists public exploit code. Fixed in github.com/woven-planet/go-zserio 0.9.1.
- Severity
- 9.8 CriticalCVSS 3.1, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
0.9.1github.com/woven-planet/go-zserio
Description
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).
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/woven-planet/go-zserioGo | before 0.9.1 | 0.9.1 |
What each source reports
GitHub Advisories Score used
go-zserio has Unbounded Memory Allocation for All Platforms
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).
- Record
GHSA-xhj4-g6w8-2xjw- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-789
- Updated
- 2026-11-02
OSV
go-zserio has Unbounded Memory Allocation for All Platforms
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).
- Record
GHSA-xhj4-g6w8-2xjw- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-789
- Updated
- 2026-11-02
OSVGO-2026-5759No score
go-zserio has Unbounded Memory Allocation for All Platforms in github.com/woven-planet/go-zserio
go-zserio has Unbounded Memory Allocation for All Platforms in github.com/woven-planet/go-zserio
- Record
GO-2026-5759- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.