Vulnerability · Published Aug 30, 2026 · Assigned by EEF
CVE-2026-80227SQL string_trim removes only spaces, diverging from in-memory trimming in AshSql
Low 2.1
In plain English
A low-severity security flaw in ash_sql from ash-project. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 31% of all known vulnerabilities).
Official description
Incorrect Comparison vulnerability in ash-project ash_sql allows a user to pad a string field with tab, newline, carriage-return, or form-feed characters and pass a trimmed uniqueness or equality check in the database that the same expression would fail in memory (or the reverse). string_trim/1 compiles to REGEXP_REPLACE patterns built from an Elixir string in which \s is the escape for a single space (codepoint 32), not a regex whitespace class. The generated SQL therefore removes only literal spaces and leaves tabs, newlines, carriage returns, and form feeds in place, whereas String.trim/1 in Elixir removes them all. Any Ash filter, validation, or identity that relies on string_trim/1 then behaves differently depending on whether Ash pushes the expression down to SQL or evaluates it in memory, so padded input can register a near-duplicate value or slip past a trimmed comparison. This issue affects ash_sql: from 0.1.0 before 0.7.1.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| ash-project | ash_sql | 0.1.0 – before 0.7.1 |
| ash-project | ash_sql | dd092ed273dec7bd2194352f24a39229fc8ae68b – before 1b11b5d8bc5321e2e6acac21594ef08f61986117 |
Weakness: CWE-697 · Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
References
- https://github.com/ash-project/ash_sql/security/advisories/GHSA-76wx-w7ww-5xfq vendor-advisory, related
- https://cna.erlef.org/cves/CVE-2026-80227.html related
- https://osv.dev/vulnerability/EEF-CVE-2026-80227 related
- https://github.com/ash-project/ash_sql/commit/1b11b5d8bc5321e2e6acac21594ef08f61986117 patch