CVE-2026-70395: ash · Improper Neutralization of Special Elements in Data Query Logic
Affects ashSource CVE Database V5
Not known to be exploited · CVSS 2.1 Low : upgrade to 3.31.1 when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.31.1, 09f42593035bceb0f6153dd7ee45cc49d108300a
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade ash to 3.31.1; ash to 09f42593035bceb0f6153dd7ee45cc49d108300a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ash-projectash | Affected
| Fixed in
|
| ash-projectash | Affected
| Fixed in
|
Hexashpkg:hex/ashOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Authorization policies remain effective, so no immediate action is required to prevent unauthorized data access beyond existing controls.
Description
CVE-2026-70395 is a low severity vulnerability in ash-project ash that allows an attacker to manipulate data query logic by submitting specially crafted lookup values. This improper neutralization of special elements in data query logic can enable an attacker to forge relationships to records they cannot name and recover secret lookup values. The issue arises when the manage_relationship function uses on_lookup: :relate on a belongs_to relationship, passing client-supplied lookup values to Ash.Query.filter/2 without proper type casting. Authorization policies remain enforced, limiting unauthorized data access.
References
- github.com/ash-project/ash/security/advisories/GHSA-vvp6-3wv6-833j (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-70395.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-70395 (opens in a new tab)
- github.com/ash-project/ash/commit/09f42593035bceb0f6153dd7ee45cc49d108300a (opens in a new tab)