CVE-2026-78691 (GCVE-0-2026-78691)
Vulnerability from cvelistv5 – Published: 2026-08-30 11:55 – Updated: 2026-08-31 14:57
VLAI
EPSS
VEX
Title
Unescaped backslash allows LIKE wildcard injection in AshSql string search
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.
Severity
SSVC
Exploitation: poc
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-08-31 14:57 UTC
CWE
- CWE-943 - Improper Neutralization of Special Elements in Data Query Logic
Assigner
References
4 references
| URL | Tags |
|---|---|
| https://github.com/ash-project/ash_sql/security/a… | vendor-advisoryrelated |
| https://cna.erlef.org/cves/CVE-2026-78691.html | related |
| https://osv.dev/vulnerability/EEF-CVE-2026-78691 | related |
| https://github.com/ash-project/ash_sql/commit/d95… | patch |
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| ash-project | ash_sql |
Affected:
0.1.1-rc.10 , < 0.7.1
(semver)
cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:* |
||
| ash-project | ash_sql |
Affected:
cfc7da474c5be2190fd62664a83a689377a8d512 , < d95c55c64b1b42cc2fd30211a4913f3145156cd4
(git)
cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:* |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-78691",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-31T14:57:20.454917Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-08-31T14:57:41.423Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/ash-project/ash_sql/security/advisories/GHSA-5jgp-7mhc-6qqh"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshSql.Expr\u0027"
],
"packageName": "ash_sql",
"packageURL": "pkg:hex/ash_sql",
"product": "ash_sql",
"programFiles": [
"lib/expr.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshSql.Expr\u0027:escape_contains/1"
},
{
"name": "\u0027Elixir.AshSql.Expr\u0027:escape_starts_with/1"
},
{
"name": "\u0027Elixir.AshSql.Expr\u0027:escape_ends_with/1"
}
],
"repo": "https://github.com/ash-project/ash_sql",
"vendor": "ash-project",
"versions": [
{
"lessThan": "0.7.1",
"status": "affected",
"version": "0.1.1-rc.10",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshSql.Expr\u0027"
],
"packageName": "ash-project/ash_sql",
"packageURL": "pkg:github/ash-project/ash_sql",
"product": "ash_sql",
"programFiles": [
"lib/expr.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshSql.Expr\u0027:escape_contains/1"
},
{
"name": "\u0027Elixir.AshSql.Expr\u0027:escape_starts_with/1"
},
{
"name": "\u0027Elixir.AshSql.Expr\u0027:escape_ends_with/1"
}
],
"repo": "https://github.com/ash-project/ash_sql",
"vendor": "ash-project",
"versions": [
{
"lessThan": "d95c55c64b1b42cc2fd30211a4913f3145156cd4",
"status": "affected",
"version": "cfc7da474c5be2190fd62664a83a689377a8d512",
"versionType": "git"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eAn application must pass untrusted input as the search term of \u003ccode\u003econtains/2\u003c/code\u003e, \u003ccode\u003estring_starts_with/2\u003c/code\u003e, or \u003ccode\u003estring_ends_with/2\u003c/code\u003e (for example a user-controlled substring search).\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "An application must pass untrusted input as the search term of `contains/2`, `string_starts_with/2`, or `string_ends_with/2` (for example a user-controlled substring search)."
}
],
"value": "An application must pass untrusted input as the search term of contains/2, string_starts_with/2, or string_ends_with/2 (for example a user-controlled substring search)."
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:*",
"versionEndExcluding": "0.7.1",
"versionStartIncluding": "0.1.1-rc.10",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Peter Ullrich"
},
{
"lang": "en",
"type": "reporter",
"value": "Peter Ullrich"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Zach Daniel / Ash Project"
},
{
"lang": "en",
"type": "coordinator",
"value": "Jonatan M\u00e4nnchen / EEF"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eImproper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sql allows a user who supplies a search term to \u003ccode\u003econtains/2\u003c/code\u003e, \u003ccode\u003estring_starts_with/2\u003c/code\u003e, or \u003ccode\u003estring_ends_with/2\u003c/code\u003e to inject live SQL \u003ccode\u003eLIKE\u003c/code\u003e wildcards, turning a literal substring search into an attacker-controlled pattern match.\u003c/p\u003e\n\u003cp\u003eThe escape helpers in \u003ccode\u003eAshSql.Expr\u003c/code\u003e prefix \u003ccode\u003e%\u003c/code\u003e and \u003ccode\u003e_\u003c/code\u003e with a backslash but never escape a backslash already present in the input. Because backslash is the default \u003ccode\u003eLIKE\u003c/code\u003e escape character, the escaping defeats itself: the input \u003ccode\u003e\\%\u003c/code\u003e becomes the pattern fragment \u003ccode\u003e\\\\%\u003c/code\u003e, where \u003ccode\u003e\\\\\u003c/code\u003e is a literal backslash and the attacker\u0027s \u003ccode\u003e%\u003c/code\u003e 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 \u003ccode\u003econtains(...)\u003c/code\u003e guard, or crash the query with a trailing lone backslash.\u003c/p\u003e\n\u003cp\u003eThis issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "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.\n\nThe 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\u0027s `%` 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.\n\nThis issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1."
}
],
"value": "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.\n\nThe 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\u0027s % 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.\n\nThis issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1."
}
],
"impacts": [
{
"capecId": "CAPEC-116",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-116 Excavation"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "LOCAL",
"baseScore": 2.1,
"baseSeverity": "LOW",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-943",
"description": "CWE-943 Improper Neutralization of Special Elements in Data Query Logic",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-30T11:55:20.331Z",
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF"
},
"references": [
{
"tags": [
"vendor-advisory",
"related"
],
"url": "https://github.com/ash-project/ash_sql/security/advisories/GHSA-5jgp-7mhc-6qqh"
},
{
"tags": [
"related"
],
"url": "https://cna.erlef.org/cves/CVE-2026-78691.html"
},
{
"tags": [
"related"
],
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-78691"
},
{
"tags": [
"patch"
],
"url": "https://github.com/ash-project/ash_sql/commit/d95c55c64b1b42cc2fd30211a4913f3145156cd4"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "Unescaped backslash allows LIKE wildcard injection in AshSql string search"
}
},
"cveMetadata": {
"assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"assignerShortName": "EEF",
"cveId": "CVE-2026-78691",
"datePublished": "2026-08-30T11:55:20.331Z",
"dateReserved": "2026-08-30T05:45:01.818Z",
"dateUpdated": "2026-08-31T14:57:41.423Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-78691",
"date": "2026-09-03",
"epss": "0.00138",
"percentile": "0.0349"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-78691\",\"sourceIdentifier\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\",\"published\":\"2026-08-30T12:17:18.550\",\"lastModified\":\"2026-09-01T21:15:00.147\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.\\n\\nThe 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\u0027s % 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.\\n\\nThis issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.\"}],\"affected\":[{\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\",\"affectedData\":[{\"vendor\":\"ash-project\",\"product\":\"ash_sql\",\"defaultStatus\":\"unaffected\",\"collectionURL\":\"https://repo.hex.pm\",\"packageName\":\"ash_sql\",\"cpes\":[\"cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:*\"],\"modules\":[\"\u0027Elixir.AshSql.Expr\u0027\"],\"programFiles\":[\"lib/expr.ex\"],\"programRoutines\":[{\"name\":\"\u0027Elixir.AshSql.Expr\u0027:escape_contains/1\"},{\"name\":\"\u0027Elixir.AshSql.Expr\u0027:escape_starts_with/1\"},{\"name\":\"\u0027Elixir.AshSql.Expr\u0027:escape_ends_with/1\"}],\"repo\":\"https://github.com/ash-project/ash_sql\",\"packageURL\":\"pkg:hex/ash_sql\",\"versions\":[{\"version\":\"0.1.1-rc.10\",\"lessThan\":\"0.7.1\",\"versionType\":\"semver\",\"status\":\"affected\"}]},{\"vendor\":\"ash-project\",\"product\":\"ash_sql\",\"defaultStatus\":\"unaffected\",\"collectionURL\":\"https://github.com\",\"packageName\":\"ash-project/ash_sql\",\"cpes\":[\"cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:*\"],\"modules\":[\"\u0027Elixir.AshSql.Expr\u0027\"],\"programFiles\":[\"lib/expr.ex\"],\"programRoutines\":[{\"name\":\"\u0027Elixir.AshSql.Expr\u0027:escape_contains/1\"},{\"name\":\"\u0027Elixir.AshSql.Expr\u0027:escape_starts_with/1\"},{\"name\":\"\u0027Elixir.AshSql.Expr\u0027:escape_ends_with/1\"}],\"repo\":\"https://github.com/ash-project/ash_sql\",\"packageURL\":\"pkg:github/ash-project/ash_sql\",\"versions\":[{\"version\":\"cfc7da474c5be2190fd62664a83a689377a8d512\",\"lessThan\":\"d95c55c64b1b42cc2fd30211a4913f3145156cd4\",\"versionType\":\"git\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV40\":[{\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"4.0\",\"vectorString\":\"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X\",\"baseScore\":2.1,\"baseSeverity\":\"LOW\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"attackRequirements\":\"PRESENT\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"vulnConfidentialityImpact\":\"LOW\",\"vulnIntegrityImpact\":\"NONE\",\"vulnAvailabilityImpact\":\"NONE\",\"subConfidentialityImpact\":\"NONE\",\"subIntegrityImpact\":\"NONE\",\"subAvailabilityImpact\":\"NONE\",\"exploitMaturity\":\"NOT_DEFINED\",\"confidentialityRequirement\":\"NOT_DEFINED\",\"integrityRequirement\":\"NOT_DEFINED\",\"availabilityRequirement\":\"NOT_DEFINED\",\"modifiedAttackVector\":\"NOT_DEFINED\",\"modifiedAttackComplexity\":\"NOT_DEFINED\",\"modifiedAttackRequirements\":\"NOT_DEFINED\",\"modifiedPrivilegesRequired\":\"NOT_DEFINED\",\"modifiedUserInteraction\":\"NOT_DEFINED\",\"modifiedVulnConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedVulnIntegrityImpact\":\"NOT_DEFINED\",\"modifiedVulnAvailabilityImpact\":\"NOT_DEFINED\",\"modifiedSubConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedSubIntegrityImpact\":\"NOT_DEFINED\",\"modifiedSubAvailabilityImpact\":\"NOT_DEFINED\",\"Safety\":\"NOT_DEFINED\",\"Automatable\":\"NOT_DEFINED\",\"Recovery\":\"NOT_DEFINED\",\"valueDensity\":\"NOT_DEFINED\",\"vulnerabilityResponseEffort\":\"NOT_DEFINED\",\"providerUrgency\":\"NOT_DEFINED\"}}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-08-31T14:57:20.454917Z\",\"id\":\"CVE-2026-78691\",\"options\":[{\"exploitation\":\"poc\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-943\"}]}],\"references\":[{\"url\":\"https://cna.erlef.org/cves/CVE-2026-78691.html\",\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\"},{\"url\":\"https://github.com/ash-project/ash_sql/commit/d95c55c64b1b42cc2fd30211a4913f3145156cd4\",\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\"},{\"url\":\"https://github.com/ash-project/ash_sql/security/advisories/GHSA-5jgp-7mhc-6qqh\",\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\"},{\"url\":\"https://osv.dev/vulnerability/EEF-CVE-2026-78691\",\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\"},{\"url\":\"https://github.com/ash-project/ash_sql/security/advisories/GHSA-5jgp-7mhc-6qqh\",\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\"}]}}",
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-78691\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"poc\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-08-31T14:57:20.454917Z\"}}}], \"references\": [{\"url\": \"https://github.com/ash-project/ash_sql/security/advisories/GHSA-5jgp-7mhc-6qqh\", \"tags\": [\"exploit\"]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-08-31T14:57:37.891Z\"}}], \"cna\": {\"title\": \"Unescaped backslash allows LIKE wildcard injection in AshSql string search\", \"source\": {\"discovery\": \"EXTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Peter Ullrich\"}, {\"lang\": \"en\", \"type\": \"reporter\", \"value\": \"Peter Ullrich\"}, {\"lang\": \"en\", \"type\": \"remediation developer\", \"value\": \"Zach Daniel / Ash Project\"}, {\"lang\": \"en\", \"type\": \"coordinator\", \"value\": \"Jonatan M\\u00e4nnchen / EEF\"}], \"impacts\": [{\"capecId\": \"CAPEC-116\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-116 Excavation\"}]}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV4_0\": {\"Safety\": \"NOT_DEFINED\", \"version\": \"4.0\", \"Recovery\": \"NOT_DEFINED\", \"baseScore\": 2.1, \"Automatable\": \"NOT_DEFINED\", \"attackVector\": \"LOCAL\", \"baseSeverity\": \"LOW\", \"valueDensity\": \"NOT_DEFINED\", \"vectorString\": \"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N\", \"providerUrgency\": \"NOT_DEFINED\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"attackRequirements\": \"PRESENT\", \"privilegesRequired\": \"NONE\", \"subIntegrityImpact\": \"NONE\", \"vulnIntegrityImpact\": \"NONE\", \"subAvailabilityImpact\": \"NONE\", \"vulnAvailabilityImpact\": \"NONE\", \"subConfidentialityImpact\": \"NONE\", \"vulnConfidentialityImpact\": \"LOW\", \"vulnerabilityResponseEffort\": \"NOT_DEFINED\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:*\"], \"repo\": \"https://github.com/ash-project/ash_sql\", \"vendor\": \"ash-project\", \"modules\": [\"\u0027Elixir.AshSql.Expr\u0027\"], \"product\": \"ash_sql\", \"versions\": [{\"status\": \"affected\", \"version\": \"0.1.1-rc.10\", \"lessThan\": \"0.7.1\", \"versionType\": \"semver\"}], \"packageURL\": \"pkg:hex/ash_sql\", \"packageName\": \"ash_sql\", \"programFiles\": [\"lib/expr.ex\"], \"collectionURL\": \"https://repo.hex.pm\", \"defaultStatus\": \"unaffected\", \"programRoutines\": [{\"name\": \"\u0027Elixir.AshSql.Expr\u0027:escape_contains/1\"}, {\"name\": \"\u0027Elixir.AshSql.Expr\u0027:escape_starts_with/1\"}, {\"name\": \"\u0027Elixir.AshSql.Expr\u0027:escape_ends_with/1\"}]}, {\"cpes\": [\"cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:*\"], \"repo\": \"https://github.com/ash-project/ash_sql\", \"vendor\": \"ash-project\", \"modules\": [\"\u0027Elixir.AshSql.Expr\u0027\"], \"product\": \"ash_sql\", \"versions\": [{\"status\": \"affected\", \"version\": \"cfc7da474c5be2190fd62664a83a689377a8d512\", \"lessThan\": \"d95c55c64b1b42cc2fd30211a4913f3145156cd4\", \"versionType\": \"git\"}], \"packageURL\": \"pkg:github/ash-project/ash_sql\", \"packageName\": \"ash-project/ash_sql\", \"programFiles\": [\"lib/expr.ex\"], \"collectionURL\": \"https://github.com\", \"defaultStatus\": \"unaffected\", \"programRoutines\": [{\"name\": \"\u0027Elixir.AshSql.Expr\u0027:escape_contains/1\"}, {\"name\": \"\u0027Elixir.AshSql.Expr\u0027:escape_starts_with/1\"}, {\"name\": \"\u0027Elixir.AshSql.Expr\u0027:escape_ends_with/1\"}]}], \"references\": [{\"url\": \"https://github.com/ash-project/ash_sql/security/advisories/GHSA-5jgp-7mhc-6qqh\", \"tags\": [\"vendor-advisory\", \"related\"]}, {\"url\": \"https://cna.erlef.org/cves/CVE-2026-78691.html\", \"tags\": [\"related\"]}, {\"url\": \"https://osv.dev/vulnerability/EEF-CVE-2026-78691\", \"tags\": [\"related\"]}, {\"url\": \"https://github.com/ash-project/ash_sql/commit/d95c55c64b1b42cc2fd30211a4913f3145156cd4\", \"tags\": [\"patch\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"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.\\n\\nThe 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\u0027s % 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.\\n\\nThis issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eImproper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sql allows a user who supplies a search term to \u003ccode\u003econtains/2\u003c/code\u003e, \u003ccode\u003estring_starts_with/2\u003c/code\u003e, or \u003ccode\u003estring_ends_with/2\u003c/code\u003e to inject live SQL \u003ccode\u003eLIKE\u003c/code\u003e wildcards, turning a literal substring search into an attacker-controlled pattern match.\u003c/p\u003e\\n\u003cp\u003eThe escape helpers in \u003ccode\u003eAshSql.Expr\u003c/code\u003e prefix \u003ccode\u003e%\u003c/code\u003e and \u003ccode\u003e_\u003c/code\u003e with a backslash but never escape a backslash already present in the input. Because backslash is the default \u003ccode\u003eLIKE\u003c/code\u003e escape character, the escaping defeats itself: the input \u003ccode\u003e\\\\%\u003c/code\u003e becomes the pattern fragment \u003ccode\u003e\\\\\\\\%\u003c/code\u003e, where \u003ccode\u003e\\\\\\\\\u003c/code\u003e is a literal backslash and the attacker\u0027s \u003ccode\u003e%\u003c/code\u003e 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 \u003ccode\u003econtains(...)\u003c/code\u003e guard, or crash the query with a trailing lone backslash.\u003c/p\u003e\\n\u003cp\u003eThis issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.\u003c/p\u003e\", \"base64\": false}, {\"type\": \"text/markdown\", \"value\": \"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.\\n\\nThe 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\u0027s `%` 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.\\n\\nThis issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-943\", \"description\": \"CWE-943 Improper Neutralization of Special Elements in Data Query Logic\"}]}], \"configurations\": [{\"lang\": \"en\", \"value\": \"An application must pass untrusted input as the search term of contains/2, string_starts_with/2, or string_ends_with/2 (for example a user-controlled substring search).\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eAn application must pass untrusted input as the search term of \u003ccode\u003econtains/2\u003c/code\u003e, \u003ccode\u003estring_starts_with/2\u003c/code\u003e, or \u003ccode\u003estring_ends_with/2\u003c/code\u003e (for example a user-controlled substring search).\u003c/p\u003e\", \"base64\": false}, {\"type\": \"text/markdown\", \"value\": \"An application must pass untrusted input as the search term of `contains/2`, `string_starts_with/2`, or `string_ends_with/2` (for example a user-controlled substring search).\", \"base64\": false}]}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"0.7.1\", \"versionStartIncluding\": \"0.1.1-rc.10\"}], \"operator\": \"OR\"}], \"operator\": \"AND\"}], \"providerMetadata\": {\"orgId\": \"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\", \"shortName\": \"EEF\", \"dateUpdated\": \"2026-08-30T11:55:20.331Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-78691\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-31T14:57:41.423Z\", \"dateReserved\": \"2026-08-30T05:45:01.818Z\", \"assignerOrgId\": \"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\", \"datePublished\": \"2026-08-30T11:55:20.331Z\", \"assignerShortName\": \"EEF\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…