Unescaped backslash allows LIKE wildcard injection in AshSql string search
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sql allows a user who supplies a search term to contains/2, string_starts_with/2, or string_ends_with/2 to inject live SQL LIKE wildcards, turning a literal substring search into an attacker-controlled pattern match. The escape helpers in AshSql.Expr prefix % and _ with a backslash but never escape a backslash already present in the input. Because backslash is the default LIKE escape character, the escaping defeats itself: the input \% becomes the pattern fragment \\%, where \\ is a literal backslash and the attacker's % remains a live wildcard. The search value stays parameterized, so this is confined to the LIKE pattern grammar rather than full SQL. An attacker can widen matches to probe values, slip past a negated contains(...) guard, or crash the query with a trailing lone backslash. This issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| ash-project | ash_sql | 0.1.1-rc.10 to before 0.7.1 | 0.7.1 | Patch available | CNA |
- ash_sql Vendorash-project Affected 0.1.1-rc.10 to before 0.7.1 Fixed in 0.7.1 Patch available CNA
CPE names CNA · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:* | — | — | — |
- cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:* Versions — — ·—
Remediation
- Fix · CNA ash_sql (ash-project) Fixed in 0.7.1
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
ash-project ash_sql 0.7.1
5 records Highest priority Priority MEDIUM 5 MEDIUM
Other records, highest priority first
- TI-2026-54013 exists/2 predicate silently dropped on limited relationships with a parent() filter in AshSqlPriority MEDIUM 60
- TI-2026-56147 Distinct-query aggregate drops the tenant schema prefix, leaking across tenants in AshSqlPriority MEDIUM 44
- TI-2026-56146 Same-named aggregates with differing filters are conflated in AshSqlPriority MEDIUM 44
Timeline
- 2026-10-02 Threatist record created from CVE-2026-78691
References
More ash-project vulnerabilities
- TI-2026-56298 Query-complexity limit bypass via first/last pagination arguments in AshGraphql enables denial of service CVSS 4.0HIGH 8.7
- TI-2026-52572 Unbounded atom creation from client-supplied RPC field names in AshTypescript field formatter CVSS 4.0HIGH 8.7
- TI-2026-57010 Path traversal in AshAdmin file uploads via unsanitized client filename CVSS 4.0HIGH 8.3
- TI-2026-26840 Ash Framework: Ash.Type.Module.cast_input/2 atom exhaustion via unchecked Module.concat allows BEAM VM crash CVSS 4.0HIGH 8.2
- TI-2026-54252 EEx template evaluation of prompt content in AshAi enables remote code execution CVSS 4.0HIGH 8.9
- TI-2026-54208 Stored XSS in AshAdmin relationship typeahead via unescaped label_field content CVSS 4.0HIGH 8.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences