Quick answers
- Is CVE-2026-86696 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86696 being exploited in the wild.
- How severe is CVE-2026-86696?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Dropbox Esaml from 0.1.0 onward.
- Is there a fix for CVE-2026-86696?
- 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-86696 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-86696?
- 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 vulnerability exists in esaml:status_code_map/1, which converts unrecognized StatusCode URN segments into Erlang atoms using list_to_atom/1. esaml_sp:validate_logout_response/2 only validates signatures when present, allowing unsigned LogoutResponse messages to reach decode_logout_response/1. An unauthenticated attacker can post millions of distinct status values to the single-logout endpoint, exhausting the Erlang VM's atom table (capped at ~1 million entries) and crashing the node.
Affected products
- Dropbox esaml from 0.1.0 onward
Timeline
- 2026-10-22: published
- 2026-10-22: disclosed