# CVE-2026-67579: Filter expression injection via forged keyset pagination cursor in Ash

> Unauthenticated attackers can inject malicious filter expressions via forged pagination cursors, leading to SQL injection or code execution in Ash applications.

- **Severity:** High 7.5 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** EEF-CVE-2026-67579, GHSA-3gq3-9xm3-c8v3

## What is CVE-2026-67579?

CVE-2026-67579 is a high-severity unsafe deserialization vulnerability in ash-project ash, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Deserialization of Untrusted Data vulnerability in ash-project ash allows an unauthenticated attacker to inject a filter expression through a forged keyset pagination cursor, resulting in SQL injection or code execution depending on the data layer.

Read actions with keyset pagination decode the client-supplied page[:after] or page[:before] cursor in decode_values/2 in lib/ash/page/keyset.ex using non_executable_binary_to_term/2 with [:safe]. That guard blocks new atoms, funs, and ports, but not a struct built from atoms already interned in a running Ash application, so a decoded %Ash.Query.Call{} expression survives and is spliced into the keyset filter as a comparison value in do_filters/4 and evaluated. Because the cursor bypasses the Ash.Expr macro, the runtime never applies the private?/public? gate that would otherwise reject it. On AshPostgres the injected fragment is inlined into the SQL query; on the ETS and Simple data layers it is evaluated in-process as an arbitrary function call.

This issue affects ash: from 1.17.0 before 3.31.3.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-502 (Deserialization of Untrusted Data)

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

1 open source package ship an affected version, including ash. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ash` | Hex | From 1.17.0 | 3.31.3 |

Products: Ash-Hq Ash Framework.

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

Upgrade ash to 3.31.3 or later.

## Is CVE-2026-67579 being exploited?

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

## Other vulnerabilities in ash-project ash

- [CVE-2026-34593](https://insights.sbomify.com/CVE-2026-34593/): Ash Framework: Ash.Type.Module.cast_input/2 atom exhaustion via unchecked Module.concat allows BEAM VM crash (high 8.2)
- [CVE-2026-69659](https://insights.sbomify.com/CVE-2026-69659/): Memory exhaustion via unbounded deserialization of keyset pagination cursors in Ash.Page.Keyset (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67579 is a high-severity unsafe deserialization vulnerability in ash-project ash, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67579 exists.

Affected packages and fixed versions:
- ash (Hex): affected from 1.17.0; fixed in 3.31.3

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-67579/ (Markdown: https://insights.sbomify.com/CVE-2026-67579/index.md)
```

## Sources

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

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