Summary
CVE-2026-93471 is a high-severity denial-of-service vulnerability (CWE-409, Improper Handling of Highly Compressed Data / Data Amplification) in esaml_binding in the esaml Erlang SAML library. An unauthenticated remote attacker can send a small, crafted compressed SAMLResponse that expands to gigabytes of memory and crashes the Erlang VM. The CNA (EEF) rates it CVSS v4.0 8.7 (High).
Technical details
- Root cause:
esaml_binding:decode_response/2base64-decodes the SAML payload, inflates it withzlib:unzip/1with no bound on output size, and converts the result to a charlist. All of this happens before any signature verification. - Trigger conditions: The application exposes a SAML endpoint (for example the assertion consumer service or single-logout endpoint) that passes attacker-supplied compressed SAML data to esaml. No authentication is needed.
- Attack vector: Network. The attacker POSTs a crafted compressed SAMLResponse. Deflate streams can reach compression ratios near 1000:1, so a payload of tens of kilobytes can expand into multiple gigabytes of heap.
- Impact: Memory exhaustion and a crash of the Erlang VM, so the service becomes unavailable (availability impact only). The record reports no confidentiality or integrity impact.
Affected software
- esaml Hex package: all versions from 0.1.0 onward, including the 3.x and 4.x branches
- dropbox/esaml: 0.1.0 and later
- handnot2/esaml and arekinath/esaml: from commit
deeb84378d5c82153b470e99d24f77c38afca14aonward
Severity
- CVSS v4.0 base score: 8.7 (High)
- Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N - The CNA published a CVSS v4.0 vector. I found no CVSS v3.1 vector for this CVE.
Mitigation and recommended actions
- Immediate: The CVE record does not name a fixed release. Patch commits are linked from the CVE record in the handnot2, arekinath and dropbox repositories. Review them and apply a patched version of esaml that bounds decompression output, as soon as one is available for your fork.
- If no patch is available: The CVE record names no official workarounds. General hardening measures include:
- Limit request body size on SAML endpoints at a reverse proxy or WAF.
- Restrict access to SAML endpoints where feasible.
- Set memory limits and process supervision so a crash is contained and recovers quickly.

