CVE-2026-86696: esaml Package Atom Table Exhaustion via Unsigned LogoutResponse

esaml Updated 22 Oct 2026

Summary

22/10/2026
No i
High
8.2

CVE-2026-86696: Unbounded atom creation from unsigned LogoutResponse status codes in esaml allows atom table exhaustion. Affects esaml across 2 version ranges.

>= 0.1.0 >= be692b56245071899757afa7ef47e43593d3de96

No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The esaml package is an implementation of SAML (Security Assertion Markup Language) for Erlang, primarily used for handling authentication and authorization in web applications. It facilitates secure communication between service providers and identity providers. However, the package is vulnerable to a specific attack that allows unauthenticated users to exploit the LogoutResponse functionality, leading to potential denial of service.

Vulnerability Detail

The vulnerability arises from the lack of signature verification for LogoutResponse messages in the esaml package. An attacker can send unsigned LogoutResponse messages with unique status codes, which are converted into permanent atoms in the Erlang VM. As the atom table has a limit of approximately one million entries, an attacker can exhaust this limit, causing the Erlang VM to crash and deny service to all users. This issue affects all versions of esaml from 0.1.0 onward.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can implement input validation on the LogoutResponse messages to reject any unsigned messages or limit the number of distinct status codes that can be processed. This can help mitigate the risk of atom table exhaustion until a patch is applied.

Conclusion

CVE-2026-86696 is a significant vulnerability in the esaml package that can lead to denial of service through atom table exhaustion. It is crucial to update the package to the latest version and implement workarounds to protect your application from potential attacks.

See every vulnerability recorded for esaml →

Share this vulnerability

FAQ

CVE-2026-86696 is a vulnerability in the esaml package that allows an attacker to exhaust the Erlang VM atom table by sending unsigned LogoutResponse messages.

If your application uses the esaml package and exposes a single-logout endpoint, it may be susceptible to denial of service attacks due to this vulnerability.

The CVSS score of this vulnerability is 8.2, indicating a high severity level.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability.

Yes, a patched version of the esaml package is available. You should update to the latest version to mitigate this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for esaml.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback