Answer in brief
CVE-2026-78691 records a Low severity (CVSS 2.1) vulnerability in Unescaped backslash allows LIKE wildcard injection in AshSql string search. The current sources do not mark it as known exploited. The current feed maps ash-project/ash-project/ash_sql (generic), ash-project/ash_sql (generic), ash-project/ash_sql (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash-project/ash-project/ash_sql (generic), ash-project/ash_sql (generic), ash-project/ash_sql (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash-project/ash_sqlgeneric | >=cfc7da474c5be2190fd62664a83a689377a8d512 <d95c55c64b1b42cc2fd30211a4913f3145156cd4 | d95c55c64b1b42cc2fd30211a4913f3145156cd4 |
| ash-project/ash_sqlgeneric | >=cfc7da474c5be2190fd62664a83a689377a8d512 <d95c55c64b1b42cc2fd30211a4913f3145156cd4 | d95c55c64b1b42cc2fd30211a4913f3145156cd4 |
| ash-project/ash_sqlgeneric | >=0.1.1-rc.10 <0.7.1 | 0.7.1 |
Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 30, 2026
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.
Quoted source text, attributed separately from HOL analysis.