CVE-2026-86696
What it is
Allocation of Resources Without Limits or Throttling vulnerability in esaml in dropbox esaml allows an unauthenticated attacker to exhaust the Erlang VM atom table and crash the node via unsigned LogoutResponse messages. esaml:status_code_map/1 in src/esaml.erl maps any StatusCode value it does not recognize to an atom with list_to_atom/1 on the last colon-separated segment of the URN. esaml_sp:validate_logout_response/2 verifies a signature only when the message carries one, so an unsigned LogoutResponse posted to the single-logout endpoint reaches esaml:decode_logout_response/1 and mints one permanent atom per distinct status value. Atoms are never reclaimed and the VM caps the atom table at about one million entries, so an attacker who posts that many distinct values aborts the node. This issue affects esaml: from 0.1.0 onward.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 0.7% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.7% in the next 30 days (EPSS).
- Severity: 8.2 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.7% · EPSS, next 30 days
- Weakness
- CWE-770 · Allocation without limits
- Record status
- Deferred
Attack profile CVSS 4.0 · 8.2
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- Present
- Privileges needed
- None
- User interaction
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-86696.md and follow it. Check whether this project is affected by CVE-2026-86696. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/arekinath/esaml/commit/be692b56245071899757afa7ef47e43593d3de96
- https://github.com/dropbox/esaml/commit/be692b56245071899757afa7ef47e43593d3de96
- https://github.com/handnot2/esaml/commit/be692b56245071899757afa7ef47e43593d3de96
References
- https://cna.erlef.org/cves/CVE-2026-86696.html
- https://github.com/arekinath/esaml/commit/be692b56245071899757afa7ef47e43593d3de96
- https://github.com/dropbox/esaml/commit/be692b56245071899757afa7ef47e43593d3de96
- https://github.com/handnot2/esaml/commit/be692b56245071899757afa7ef47e43593d3de96
- https://osv.dev/vulnerability/EEF-CVE-2026-86696
- https://cna.erlef.org/cves/CVE-2026-86696.html
- https://osv.dev/vulnerability/EEF-CVE-2026-86696