CVE-2026-74837
Attacker-controlled RPC field names can exhaust BEAM atom table and crash nodes.
Is CVE-2026-74837 being exploited?
Not confirmed. CVE-2026-74837 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-74837?
CVE-2026-74837 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74837?
Yes. A fix has been recorded for CVE-2026-74837. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74837 affect?
CVE-2026-74837 affects ash_typescript >=0.1.0 <0.18.0, ash-project ash_typescript library, Elixir/BEAM nodes using ash_typescript. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74837?
Upgrade to ash_typescript >=0.18.0 and validate/limit RPC field names and rate-limit RPCs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote denial-of-service: unauthenticated attacker can mint atoms via RPC field names to exhaust BEAM atom table and abort the VM; >255-char names may raise SystemLimitError.
Immediate action required
- affected>= 0.1.0 and < 0.18.0
- affected>= 1a3d4c343430c8e4784acfcd33122a807fafa086 and < df95df4b9afdca5e5bbce32dbd566ccc49a7f14b
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.