{"answers":{"affected":"1 open source package ship an affected version, including ash_typescript.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77856 exists.","fix":"Upgrade ash_typescript to 0.18.0 or later.","what":"CVE-2026-77856 is a high-severity denial of service vulnerability in ash-project ash_typescript, published on 1 Sep 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-77856 and fix it if it is affected.\n\nWhat it is: CVE-2026-77856 is a high-severity denial of service vulnerability in ash-project ash_typescript, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77856 exists.\n\nAffected packages and fixed versions:\n- ash_typescript (Hex): affected from 0.11.0; fixed in 0.18.0\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-77856/ (Markdown: https://insights.sbomify.com/CVE-2026-77856/index.md)","id":"CVE-2026-77856","markdown":"https://insights.sbomify.com/CVE-2026-77856/index.md","name":"CVE-2026-77856","record":{"aliases":["EEF-CVE-2026-77856","GHSA-rj47-h936-4cxw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir Ash library","requires_auth":"none","summary":"An unauthenticated attacker can crash the Elixir node by exhausting the atom table via crafted field names in AshTypescript.","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":"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 typed struct field names.\n\nresolve_typed_struct_field/2 in lib/ash_typescript/rpc/field_processing/field_selector.ex looks a client-supplied field name up in the typed struct's reverse map and, when it finds no match, falls back to String.to_atom/1. Because this runs before any field-existence check, an unresolvable name mints a permanent atom rather than being rejected as unknown. Atoms are never garbage collected, so a request carrying many distinct names on a typed struct field grows the atom table until the VM aborts at its limit.\n\nThis issue affects ash_typescript: from 0.11.0 before 0.18.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Unbounded atom creation from typed struct field names in AshTypescript field selector","id":"CVE-2026-77856","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":"'serve-expired' can bypass Unbound 'wait-limit'","id":"CVE-2026-77860"},"packages":[{"ecosystem":"Hex","fixed":["0.18.0"],"introduced":["0.11.0"],"last_affected":[],"package":"ash_typescript","purl":"pkg:hex/ash_typescript","source":"EEF-CVE-2026-77856"}],"prev":{"headline":"Command injection in FF-RFI078I4","id":"CVE-2026-77853"},"products":["ash_typescript"],"published":"2026-09-01","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["ash-project"]},"summary":"An unauthenticated attacker can crash the Elixir node by exhausting the atom table via crafted field names in AshTypescript.","url":"https://insights.sbomify.com/CVE-2026-77856/"}