PatchSiren cyber security CVE debrief
CVE-2026-33524 ndsev CVE debrief
A crafted payload can cause a Denial of Service (OOM error) in Zserio versions prior to 2.18.1. This vulnerability allows an attacker to crash any process with an OOM error by forcing memory allocations of up to 16 GB with a payload as small as 4-5 bytes. Defenders should assess exposure and verify versions to mitigate potential impacts. The CVE record and NVD entry provide details on the vulnerability and fixed version, which defenders can use to prioritize verifying Zserio versions and restricting exposure to untrusted payloads.
- Vendor
- ndsev
- Product
- zserio
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-24
- Original CVE updated
- 2026-10-26
- Advisory published
- 2026-04-24
- Advisory updated
- 2026-10-26
Who should care
Defenders responsible for Zserio deployments should assess exposure and verify versions to mitigate potential impacts. This includes operators, platform administrators, vulnerability management teams, and security teams who need to prioritize verifying Zserio versions and restricting exposure to untrusted payloads. Defenders should also review compensating controls for exposed systems and monitor for OOM errors to prevent potential Denial of Service (OOM)
Why it matters
Defenders should prioritize verifying Zserio versions and restricting exposure to untrusted payloads to prevent potential Denial of Service (OOM error).
- Potential Denial of Service (OOM error) in Zserio deployments
- Need to verify Zserio version and restrict exposure to untrusted payloads
Technical summary
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) in Zserio versions prior to 2.18.1. This vulnerability allows an attacker to cause a Denial of Service by exploiting the inefficient serialization mechanism in Zserio. The vulnerability is fixed in Zserio version 2.18.1, which defenders should prioritize verifying and deploying to prevent potential impacts. The CVE record and NVD entry provide additional technical details on the vulnerability.
Defensive priority
Defenders should prioritize verifying Zserio versions and restricting exposure to untrusted payloads.
Recommended defensive actions
- Verify Zserio version is 2.18.1 or later
- Restrict exposure to untrusted payloads
- Monitor for OOM errors
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability and fixed version. The vulnerability is fixed in Zserio version 2.18.1. Defenders should verify Zserio versions and restrict exposure to untrusted payloads to prevent potential Denial of Service (OOM error). The CVE record was published on 2026-04-24T19:17:09.850Z and has not been modified since then. The official CVE Program record and NIST NVD detail page offer additional information on the vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-33524 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-33524
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-33524 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-33524
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/ndsev/zserio/security/advisories/GHSA-cwq5-8pvq-j65j
[email protected] - Exploit, Mitigation, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.