{"answers":{"affected":"1 open source package ship an affected version, including ash.","exploited":"There is no known exploitation of CVE-2026-94201 in the wild and no public exploit code.","fix":"Upgrade ash to 3.34.3 or later.","what":"CVE-2026-94201 is a high-severity denial of service vulnerability in ash-project ash, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-94201 and fix it if it is affected.\n\nWhat it is: CVE-2026-94201 is a high-severity denial of service vulnerability in ash-project ash, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-94201 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ash (Hex): affected from 3.5.1; fixed in 3.34.3\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-94201/ (Markdown: https://insights.sbomify.com/CVE-2026-94201/index.md)","id":"CVE-2026-94201","markdown":"https://insights.sbomify.com/CVE-2026-94201/index.md","name":"CVE-2026-94201","record":{"aliases":["EEF-CVE-2026-94201","GHSA-hh99-hqg5-6646"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Elixir Ash framework","requires_auth":"none","summary":"Attackers can crash the BEAM node by exhausting the atom table via filter inputs on attributes configured with unsafe_to_atom?.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Ash stores :atom-typed attributes as strings and compares them as strings. When such an attribute is referenced in a filter, the comparison value is coerced through Ash.Type.Atom. Because the type defined no coerce/2 callback, coercion fell back to the default (cast_input/2), which calls String.to_atom/1 when the attribute is configured with the unsafe_to_atom?: true constraint.\n\nFiltering such an attribute with attacker-controlled strings therefore interned a new, permanent atom for every distinct value. Atoms are never garbage collected and the BEAM caps the atom table, so an actor who can supply filter values for a public, filterable :atom attribute declared with unsafe_to_atom?: true can exhaust the atom table and crash the node (denial of service). AshPaperTrail is a notable example: its version resources expose a public, filterable version_action_name atom attribute with unsafe_to_atom?: true by default.\n\nThe fix adds a coerce/2 to Ash.Type.Atom that never interns atoms — a comparison value is left as a string, since the type is stored and compared as a string. Setting the attribute from action input (cast_input/2, which still honors unsafe_to_atom?) is unchanged.\n\nThis issue affects ash: from 3.5.1 before 3.34.3.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Filtering an :atom attribute with unsafe_to_atom? can exhaust the BEAM atom table in Ash","id":"CVE-2026-94201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Module block-pool create validates two of the four parameter words it reads","id":"CVE-2026-94202"},"packages":[{"ecosystem":"Hex","fixed":["3.34.3"],"introduced":["3.5.1"],"last_affected":[],"package":"ash","purl":"pkg:hex/ash","source":"EEF-CVE-2026-94201"}],"prev":{"headline":"TLS 1.3 client ticket store crashed by NewSessionTicket with empty early_data extension in ssl","id":"CVE-2026-94200"},"products":["ash"],"published":"2026-10-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-06","vendors":["ash-project"]},"summary":"Attackers can crash the BEAM node by exhausting the atom table via filter inputs on attributes configured with unsafe_to_atom?.","url":"https://insights.sbomify.com/CVE-2026-94201/"}