Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-93471 – Denial of Service (Decompression Bomb) – esaml 0.1.0 and later (Erlang SAML library

Be the first to know when new zero-days emerge:

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/2 base64-decodes the SAML payload, inflates it with zlib:unzip/1 with 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 deeb84378d5c82153b470e99d24f77c38afca14a onward

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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge