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.
{
"cna_assigner": "EEF",
"cwe_ids": [
"CWE-943"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/78xxx/CVE-2026-78691.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"introduced": "cfc7da474c5be2190fd62664a83a689377a8d512"
},
{
"fixed": "d95c55c64b1b42cc2fd30211a4913f3145156cd4"
}
],
"source": "AFFECTED_FIELD"
}
]
}