Quick answers
- Is CVE-2026-93471 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93471 being exploited in the wild.
- How severe is CVE-2026-93471?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Dropbox Esaml 0.1.0 and later.
- Is there a fix for CVE-2026-93471?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93471 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93471?
- Check whether you run Dropbox Esaml at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The esaml_binding:decode_response/2 function base64-decodes and inflates a SAML response using zlib without limiting decompression output, then converts the result to a charlist before parsing. The vulnerability is exposed on SAML ACS (assertion consumer service) and single-logout endpoints which accept unauthenticated requests by design. An attacker can craft a deflate stream with a compression ratio near 1000:1, causing tens of kilobytes of input to expand to gigabytes, exhausting heap memory and crashing the Erlang VM.
Affected products
- Dropbox esaml 0.1.0 and later
Timeline
- 2026-10-22: disclosed