SQL string_trim removes only spaces, diverging from in-memory trimming in AshSql (CVE-2026-80227) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80227

SQL string_trim removes only spaces, diverging from in-memory trimming in AshSql

Answer in brief

CVE-2026-80227 records a Unknown severity vulnerability in SQL string_trim removes only spaces, diverging from in-memory trimming in AshSql. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_sql (generic), ash-project/ash_sql (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 30, 2026Updated Aug 30, 2026Source checked Aug 30, 2026First seen by HOL Aug 30, 2026Material review Aug 30, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ash-project/ash_sql (generic), ash-project/ash_sql (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ash-project/ash_sqlgeneric	>=0.1.0 <0.7.1	0.7.1
ash-project/ash_sqlgeneric	>=dd092ed273dec7bd2194352f24a39229fc8ae68b <1b11b5d8bc5321e2e6acac21594ef08f61986117	1b11b5d8bc5321e2e6acac21594ef08f61986117

Recommended response

Check inventory. Check lockfiles and deployed manifests for ash-project/ash_sql, ash-project/ash_sql.
Review the reported fix. Update ash-project/ash_sql to 0.7.1; ash-project/ash_sql to 1b11b5d8bc5321e2e6acac21594ef08f61986117 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 30, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.