🛡️ CVE-2026-33524 — zserio
Description
Zserio Runtime: Integer Overflow in BitStreamReader and Unbounded Memory Allocation in Deserialization
Summary
Unbounded Memory Allocation (all platforms)
A crafted payload as small as 4-5 bytes can force memory allocations of up to 16 GB, crashing any process with an OOM error (Denial of Service).
Affected code (C++):
cpp/runtime/src/zserio/Array.h(line 1029) —m_rawArray.reserve(readLength)with uncheckedreadLengthcpp/runtime/src/zserio/BitStreamReader.h(lines 249, 281) —value.reserve(len)with uncheckedlen
Affected code (Java):
java/runtime/src/zserio/runtime/array/Array.java(line 271) —rawArray.reset(readSize)→new int[readSize]java/runtime/src/zserio/runtime/io/ByteArrayBitStreamReader.java(line 245) —new byte[length]
Proof of Concept
Memory Allocation DoS (verified on 64-bit)
| Payload | Claimed Size | Allocated | Amplification |
|---------|-------------|-----------|---------------|
| 4 bytes | 100,000,000 | 762 MB | ~200 million x |
| 5 bytes | 2,147,483,647 | ~16 GB | system crash |
The full PoC source code and Docker build files are available upon request.
Impact
zserio is the serialization framework underlying the NDS (Navigation Data Standard), used by 43 member companies including Toyota, BMW, Volkswagen, Mercedes-Benz, and others. According to the Eclipse zserio project:
> "Zserio serialized data is used in millions of deployments in cars on the road"
Attack vectors include NDS.Live cloud map updates, map data supply chain compromise, and backend data processing pipelines. On 32-bit automotive ECUs, this could affect ADAS functionality.
Suggested Fix
For all runtimes: Validate varsize against stream size
```
if (claimedSize > remainingBytesInStream) {
throw error("varsize claims more data than available in stream");
}
```
Disclosure Timeline
- 2026-03-08: Reported to Woven by Toyota PSIRT (go-zserio)
- 2026-03-10: Reported to ndsev/zserio maintainers via GitHub Security Advisory
- 2026-03-23: Split off overflow vulnerability to own report
- 90-day coordinated disclosure timeline
A patch for this issue is available at https://github.com/ndsev/zserio/releases/tag/v2.18.1.
Reporter
Ryuji Yasukochi ([email protected])
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
Weakness class
CVE-2026-33524 is classified as CWE-789: Memory Allocation with Excessive Size Value. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.
Affected software
CVE-2026-33524 is recorded against 2 packages.
- io.github.ndsev:zserio-runtime (fixed in 2.18.1)
- zserio (fixed in 2.18.1)
Timeline and source
Published on 24 April 2026 and last revised on 5 May 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| io.github.ndsev:zserio-runtime | — | 2.18.1 |
| zserio | — | 2.18.1 |
References
Site Security Check
Is zserio part of your stack?
CVE-2026-33524 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.