Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-105270 – Denial of Service (Atom Table Exhaustion) – esaml (dropbox/esaml ≥ 0.1.0, handnot2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-105270 is an unbounded resource allocation vulnerability (CWE-770) in esaml, an Erlang SAML library. An unauthenticated remote attacker can exhaust the Erlang VM’s atom table and crash the node by sending crafted SAML messages. The CNA rates it High (CVSS 8.7).

Technical details

  • Root cause: esaml_binding:decode_response/2 parses SAML responses with xmerl_scan:string/2. That call converts every element name, attribute name and namespace prefix into permanent atoms.
  • Trigger conditions: The service accepts SAML responses from unauthenticated clients, and the parsing happens before any authentication or signature check. A well-formed document with thousands of distinct names creates thousands of atoms while staying within a 128 KB request body limit.
  • Attack vector: Network. No privileges and no user interaction are required.
  • Impact: Atoms are never garbage-collected, and the VM caps the atom table at roughly one million entries. The CNA states that dozens of crafted requests can crash the node, which is a denial of service on availability only.

Affected software

  • dropbox/esaml: version 0.1.0 and later
  • handnot2/esaml: version 2.0.0 and later
  • arekinath/esaml: all versions from commit deeb84378d5c82153b470e99d24f77c38afca14a

Severity

  • CVSS v4.0 base score 8.7 (High), as published by the CNA (EEF).
  • 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
  • The published record uses CVSS v4.0. I did not find a v3.1 score.

Mitigation and recommended actions

  • Immediate: The CVE record documents no fixed release and no workarounds. The record references commits in the affected repositories. Check the maintainers’ repositories and the EEF CNA record for updates.
  • Interim: Identify applications that use esaml to receive SAML responses. Apply request-size and rate limiting in front of SAML endpoints, and monitor Erlang VM atom count. These measures are general hardening and are not vendor-documented workarounds.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge