ash-project ash up to 3.31.2 Keyset Pagination lib/ash/page/keyset.ex decode_values after/before sql injection

Summaryinfo

A vulnerability was found in ash-project ash up to 3.31.2. It has been classified as critical. This impacts the function decode_values of the file lib/ash/page/keyset.ex of the component Keyset Pagination. This manipulation of the argument after/before causes sql injection. This vulnerability appears as CVE-2026-67579. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as critical was found in ash-project ash up to 3.31.2. Affected by this vulnerability is the function decode_values of the file lib/ash/page/keyset.ex of the component Keyset Pagination. The manipulation of the argument after/before with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-67579 since 08/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 3.31.3 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Project Management Software

Vendor

• ash-project

Name

• ash

Version

• 3.31.0
• 3.31.1
• 3.31.2

Website

• Product: https://github.com/ash-project/ash/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion