{"answers":{"affected":"1 open source package ship an affected version, including ash_sql.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78691 exists.","fix":"Upgrade ash_sql to 0.7.1 or later.","what":"CVE-2026-78691 is a low-severity SQL injection vulnerability in ash-project ash_sql, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-78691 and fix it if it is affected.\n\nWhat it is: CVE-2026-78691 is a low-severity SQL injection vulnerability in ash-project ash_sql, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78691 exists.\n\nAffected packages and fixed versions:\n- ash_sql (Hex): affected from 0.1.1-rc.10; fixed in 0.7.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-78691/ (Markdown: https://insights.sbomify.com/CVE-2026-78691/index.md)","id":"CVE-2026-78691","markdown":"https://insights.sbomify.com/CVE-2026-78691/index.md","name":"CVE-2026-78691","record":{"aliases":["EEF-CVE-2026-78691","GHSA-5jgp-7mhc-6qqh"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir SQL library","requires_auth":"none","summary":"Attackers can inject SQL LIKE wildcards in AshSql string searches to bypass filters, probe data, or cause denial of service.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"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"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"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'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.\n\nThis issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Unescaped backslash allows LIKE wildcard injection in AshSql string search","id":"CVE-2026-78691","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Incomplete redaction re-attaches the original error path in AshGraphql, leaking internal field names","id":"CVE-2026-78693"},"packages":[{"ecosystem":"Hex","fixed":["0.7.1"],"introduced":["0.1.1-rc.10"],"last_affected":[],"package":"ash_sql","purl":"pkg:hex/ash_sql","source":"EEF-CVE-2026-78691"}],"prev":{"headline":"NGINX ngx_http_js_module vulnerablility","id":"CVE-2026-78689"},"products":["ash_sql"],"published":"2026-08-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["ash-project"]},"summary":"Attackers can inject SQL LIKE wildcards in AshSql string searches to bypass filters, probe data, or cause denial of service.","url":"https://insights.sbomify.com/CVE-2026-78691/"}