# CVE-2026-82722: AshAdmin LiveView events intern atoms from client input, exhausting the atom table (node DoS)

> Attackers can crash the entire Elixir node by exhausting the atom table via unvalidated client input in AshAdmin LiveView events.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** EEF-CVE-2026-82722, GHSA-wcr6-9rrw-5jhv

## What is CVE-2026-82722?

CVE-2026-82722 is a high-severity denial of service vulnerability in ash-project ash_admin, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Allocation of Resources Without Limits or Throttling vulnerability in ash-project ash_admin lets any client that can reach the admin LiveView exhaust the BEAM atom table and crash the entire node.

Two LiveView event handlers interned atoms from unvalidated client input: AshAdmin.PageLive's set_actor built modules from the resource/domain payload with Module.concat/1, and AshAdmin.Components.Resource.Show's calculate converted every submitted form key with String.to_atom/1. Atoms are never garbage collected and the table is capped, so flooding either event with random names mints a new atom per request until the VM aborts, taking down every application on the node. The fix resolves the submitted resource/domain against the known shown resources and maps calculation keys to declared arguments, so no client-supplied string is interned.

This issue affects ash_admin: from 0.1.0 before 1.3.1.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-82722?

1 open source package ship an affected version, including ash_admin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ash_admin` | Hex | From 0.1.0 | 1.3.1 |

## How do I fix CVE-2026-82722?

Upgrade ash_admin to 1.3.1 or later.

## Is CVE-2026-82722 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82722 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82722 and fix it if it is affected.

What it is: CVE-2026-82722 is a high-severity denial of service vulnerability in ash-project ash_admin, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82722 exists.

Affected packages and fixed versions:
- ash_admin (Hex): affected from 0.1.0; fixed in 1.3.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82722/ (Markdown: https://insights.sbomify.com/CVE-2026-82722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82722
- OSV: https://osv.dev/vulnerability/CVE-2026-82722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82722/
Summaries are generated and may contain mistakes; the official description above is the record.