CVE-2026-74837

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Allocation of Resources Without Limits or Throttling vulnerability in ash-project ash_typescript allows an unauthenticated attacker to exhaust the BEAM atom table and abort the node via client-supplied RPC field names.

AshTypescript.FieldFormatter.convert_to_field_atom/2 in lib/ash_typescript/field_formatter.ex converts a client-supplied field name to an atom with String.to_atom/1 when no matching atom already exists. It delegates first to parse_input_field/2, which resolves the name with String.to_existing_atom/1 and falls back to returning the plain string; convert_to_field_atom/2 then mints an atom from that string rather than treating the name as unknown.

RPC field selection reaches it for every requested field name through AshTypescript.Rpc.FieldProcessing.FieldSelector, which resolves each name before checking that the field exists, with no allowlist, length bound, or rate limit. Atoms are never garbage collected, so each distinct name mints a permanent one and the VM aborts once the atom table limit is reached. A field name over 255 characters additionally raises an uncaught SystemLimitError.

This issue affects ash_typescript: from 0.1.0 before 0.18.0.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
70(Attend)
EG Risk 70/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Sep 1, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available

commit df95df4b9afd (ash-project/ash_typescript)

Patch available: ash-project/ash_typescript v0.18.0 (contains commit df95df4b9afd)

https://github.com/ash-project/ash_typescript/commit/df95df4b9afdca5e5bbce32dbd566ccc49a7f14b
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-74837
generic

CVE-2026-74837

https://cna.erlef.org/cves/CVE-2026-74837.html
github Patch Available🟡 PoC Available

AshTypescript vulnerable to BEAM atom table exhaustion via client-supplied RPC field names · Advisory · ash-project/ash_typescript · GitHub

https://github.com/ash-project/ash_typescript/security/advisories/GHSA-mhxc-mhqx-3v28

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash_typescript0.1.0 ... 0.9.1 (51 versions)0.18.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 16:45 UTCEG score recompute
  2. 2026-09-19 04:32 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 03:46 UTCEG score recompute
  5. 2026-09-16 15:07 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 14:40 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 01:59 UTCEG score recompute
  11. 2026-09-13 01:33 UTCEG score recompute
  12. 2026-09-12 15:02 UTCEPSS rescore
  13. 2026-09-12 01:07 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 12:54 UTCEG score recompute
  16. 2026-09-10 12:06 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-08 23:28 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-08 03:09 UTCEG score recompute
  21. 2026-09-07 00:26 UTCEG score recompute
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-05 23:54 UTCEG score recompute
  24. 2026-09-04 23:28 UTCEG score recompute
  25. 2026-09-04 10:37 UTCEG score recompute
Show 9 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 21:53 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 16:28 UTCEG score recompute
  5. 2026-09-01 15:56 UTCEG score recompute
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 03:28 UTCEG score recompute
  8. 2026-09-01 02:36 UTCEG score recompute
  9. 2026-09-01 02:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74837?
CVE-2026-74837 is a high vulnerability published on September 1, 2026. Allocation of Resources Without Limits or Throttling vulnerability in ash-project ash_typescript allows an unauthenticated attacker to exhaust the BEAM atom table and abort the node via client-supplied RPC field names. AshTypescript.FieldFormatter.converttofieldatom/2 in…
When was CVE-2026-74837 disclosed?
CVE-2026-74837 was first published in the National Vulnerability Database on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74837 actively exploited?
CVE-2026-74837 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-74837?
CVE-2026-74837 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-74837?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74837, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74837

Explore →

Is Your Infrastructure Affected by CVE-2026-74837?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs