Answer in brief
CVE-2026-77846 records a Low severity (CVSS 2.1) vulnerability in JSON path injection via unescaped get_path segments in AshSqlite. The current sources do not mark it as known exploited. The current feed maps ash-project/ash-project/ash_sqlite (generic), ash-project/ash_sqlite (generic), ash-project/ash_sqlite (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.1. 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.
The current feed maps ash-project/ash-project/ash_sqlite (generic), ash-project/ash_sqlite (generic), ash-project/ash_sqlite (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash-project/ash_sqlitegeneric | >=c12be48a5b6295593199b0e445b70a4aef81d1cd <2138480fceb654bec1845e691517ac409d0232c3 | 2138480fceb654bec1845e691517ac409d0232c3 |
| ash-project/ash_sqlitegeneric | >=c12be48a5b6295593199b0e445b70a4aef81d1cd <2138480fceb654bec1845e691517ac409d0232c3 | 2138480fceb654bec1845e691517ac409d0232c3 |
| ash-project/ash_sqlitegeneric | >=0.1.2-rc.0 <0.2.18 | 0.2.18 |
Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 30, 2026
Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sqlite allows an attacker who controls a get_path/2 segment to traverse into nested JSON the application never exposed, disclosing private or sensitive? embedded fields. AshSqlite.SqlImplementation builds the SQLite json_extract path with "$." <> Enum.join(right, "."), so a single segment containing ., [, ], or $ re-interprets the JSON path (for example "private.secret" descends two levels instead of naming one key). The path is bound as a parameter, so this is confined to the JSON-path grammar rather than SQL. Any endpoint that lets user input reach a get_path segment (a common pick-a-field pattern) can read nested values it never meant to expose. This issue affects ash_sqlite: from 0.1.2-rc.0 before 0.2.18.
Quoted source text, attributed separately from HOL analysis.