Description (CNA)
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.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| ash-project / ash_sqlite | affected 0.1.2-rc.0 before 0.2.18 |
| ash-project / ash_sqlite | affected c12be48a5b6295593199b0e445b70a4aef81d1cd before 2138480fceb654bec1845e691517ac409d0232c3 |
CWE
CWE-943
References
- https://github.com/ash-project/ash_sqlite/security/advisories/GHSA-hrp2-5hgw-c83c
- https://cna.erlef.org/cves/CVE-2026-77846.html
- https://osv.dev/vulnerability/EEF-CVE-2026-77846
- https://github.com/ash-project/ash_sqlite/commit/2138480fceb654bec1845e691517ac409d0232c3
ADP enrichment
No English description supplied.