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


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** EEF-CVE-2026-105270, GHSA-6m7w-85hw-3q64

## What is CVE-2026-105270?

CVE-2026-105270 is a high-severity vulnerability in arekinath esaml, published on 22 Oct 2026. 

### Official 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-105270?

1 open source package ship an affected version, including esaml.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `esaml` | Hex | From 0.1.0 | None |

## How do I fix CVE-2026-105270?

No fix has been published for CVE-2026-105270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105270 being exploited?

There is no known exploitation of CVE-2026-105270 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105270 and fix it if it is affected.

What it is: CVE-2026-105270 is a high-severity vulnerability in arekinath esaml, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-105270 in the wild and no public exploit code.

Affected packages and fixed versions:
- esaml (Hex): affected from 0.1.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105270/ (Markdown: https://insights.sbomify.com/CVE-2026-105270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105270
- OSV: https://osv.dev/vulnerability/CVE-2026-105270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105270/
Summaries are generated and may contain mistakes; the official description above is the record.