CVE-2026-70395
Last modified
CVE-2026-70395 is a low-severity vulnerability rated 2.1/10 on the CVSS scale. Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash allows an attacker to forge a relationship to a record they cannot name, and to recover the secret value used to look it up. When manage_relationship is used with on_lookup: :relate on a belongs_to relationship, the client-supplied lookup value is passed to Ash.Query.filter/2 without being cast to the attribute type. A nested map submitted where a scalar is expected is therefore interpreted as a filter predicate rather than a literal, so a lookup for a specific record becomes a query for any record matching a condition. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash allows an attacker to forge a relationship to a record they cannot name, and to recover the secret value used to look it up. When manage_relationship is used with on_lookup: :relate on a belongs_to relationship, the client-supplied lookup value is passed to Ash.Query.filter/2 without being cast to the attribute type. A nested map submitted where a scalar is expected is therefore interpreted as a filter predicate rather than a literal, so a lookup for a specific record becomes a query for any record matching a condition. The same path omits Ash.Query.limit(1), leaving Ash.read_one/2 able to distinguish no match from one match from several, which turns comparison predicates into an oracle for the lookup value. Authorization is unaffected; the destination read policy still applies. This issue affects ash: from 1.52.0-rc.11 before 3.31.1.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| ash-project | ash | >= 1.52.0-rc.11, < 3.31.1 |
| ash-project | ash | >= 571c138140e71cea24005189f45d7a63c8d2ed20, < 09f42593035bceb0f6153dd7ee45cc49d108300a |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-70395?
How severe is CVE-2026-70395?
How do I fix CVE-2026-70395?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-70382Some externally supplied values stored by the device may be …4.1
- CVE-2026-70383Improper Limitation of a Pathname to a Restricted Directory …8.4
- CVE-2026-70386Improper neutralization of special elements used in an OS co…8.5
- CVE-2026-70387Exposed dangerous method or function and Incorrect Authoriza…8.4
- CVE-2026-70388SOEM version 2.0.0 and earlier contains vulnerabilities wher…8.3
- CVE-2026-7039A security vulnerability has been detected in tufantunc ssh-…7.8
- CVE-2026-70396Gitea's organization repository-creation API requires write:…5.4
- CVE-2026-70398A flaw was found in multicloud-integrations, a component of …9.6
- CVE-2026-70399Allocation of Resources Without Limits or Throttling vulnera…8.7
- CVE-2026-7040Text::Minify::XS versions from 0.3.0 before 0.7.8 for Perl h…7.5
- CVE-2026-70400Gitea's repository migration API accepts a public-only token…5.4
- CVE-2026-70402Gitea creates server-side Git hook directories and scripts w…5.8
Are you affected by CVE-2026-70395?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
