Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-74837 – Denial of Service (BEAM Atom Table Exhaustion) – ash_typescript 0.1.0 through 0.17.

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-74837 is a high-severity denial-of-service vulnerability in ash_typescript, an Elixir/Ash Framework library that generates TypeScript RPC clients. An unauthenticated remote attacker can supply arbitrary, malicious field names in RPC requests, causing the application to convert them into BEAM atoms without validation. Because atoms are never garbage-collected by the Erlang VM, repeated exploitation exhausts the atom table and crashes the entire BEAM node, taking down every application running on it.

Technical details

  • Root cause: AshTypescript.FieldFormatter.convert_to_field_atom/2 converts client-supplied field name strings into atoms using String.to_atom/1 without checking them against an allowlist of known/expected atoms.
  • Contributing factors: parse_input_field/2 falls back to returning plain strings for unresolved input, which are subsequently converted into permanent atoms, and AshTypescript.Rpc.FieldProcessing.FieldSelector processes every incoming field name before any validation occurs — there are no length checks, rate limits, or allowlists anywhere in the path.
  • Trigger conditions: No authentication or special privileges are required; an attacker simply sends RPC requests containing unique, arbitrary field names to any exposed AshTypescript RPC endpoint.
  • Attack vector: Network-based (AV:N), low attack complexity, no user interaction required.
  • Impact: Each unique attacker-supplied field name permanently consumes space in the BEAM VM’s atom table (limited to roughly 1,048,576 entries by default). Once the table is exhausted, the entire BEAM node aborts, causing a full denial of service for the application and any other services co-located on that node. Recovery requires a node restart.

Affected software

  • ash_typescript (ash-project), versions 0.1.0 through 0.17.x (all versions prior to 0.18.0)
  • Distributed via hex.pm and GitHub

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • 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
  • No confidentiality or integrity impact; severe availability impact only.

Mitigation and recommended actions

  • Immediate: Upgrade ash_typescript to version 0.18.0 or later, which adds validation to prevent unbounded, unauthenticated atom creation from user-supplied RPC field names.
  • If immediate patching is not possible: No effective application-level workaround exists for versions prior to 0.18.0. Security teams should consider restricting or monitoring access to exposed AshTypescript RPC endpoints (e.g., via network-layer access controls or WAF rules limiting unusual/high-cardinality field-name parameters) as a temporary compensating control until the upgrade can be applied, and should plan for prompt node restarts and monitoring of BEAM atom table utilization as an interim detection measure.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge