# CVE-2026-80227: SQL string_trim removes only spaces, diverging from in-memory trimming in AshSql

> Attackers can bypass uniqueness or equality checks by padding strings with whitespace characters that are not trimmed in SQL, leading to duplicate data or validation bypasses.

- **Severity:** Low 2.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** EEF-CVE-2026-80227, GHSA-76wx-w7ww-5xfq

## What is CVE-2026-80227?

CVE-2026-80227 is a low-severity 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.

### 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.

Weakness: CWE-697 (Incorrect Comparison)

## Which versions are affected by CVE-2026-80227?

1 open source package ship an affected version, including ash_sql.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ash_sql` | Hex | From 0.1.0 | 0.7.1 |

## How do I fix CVE-2026-80227?

Upgrade ash_sql to 0.7.1 or later.

## Is CVE-2026-80227 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80227 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80227 and fix it if it is affected.

What it is: CVE-2026-80227 is a low-severity 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80227 exists.

Affected packages and fixed versions:
- ash_sql (Hex): affected from 0.1.0; fixed in 0.7.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80227/ (Markdown: https://insights.sbomify.com/CVE-2026-80227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80227
- OSV: https://osv.dev/vulnerability/CVE-2026-80227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80227/
Summaries are generated and may contain mistakes; the official description above is the record.