CVE-2026-77846 (GCVE-0-2026-77846)
Vulnerability from cvelistv5 – Published: 2026-08-30 02:52 – Updated: 2026-08-30 02:52
VLAI
EPSS
VEX
Title
JSON path injection via unescaped get_path segments in AshSqlite
Summary
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.
Severity
CWE
- CWE-943 - Improper Neutralization of Special Elements in Data Query Logic
Assigner
References
4 references
| URL | Tags |
|---|---|
| https://github.com/ash-project/ash_sqlite/securit… | vendor-advisoryrelated |
| https://cna.erlef.org/cves/CVE-2026-77846.html | related |
| https://osv.dev/vulnerability/EEF-CVE-2026-77846 | related |
| https://github.com/ash-project/ash_sqlite/commit/… | patch |
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| ash-project | ash_sqlite |
Affected:
0.1.2-rc.0 , < 0.2.18
(semver)
cpe:2.3:a:ash-project:ash_sqlite:*:*:*:*:*:*:*:* |
||
| ash-project | ash_sqlite |
Affected:
c12be48a5b6295593199b0e445b70a4aef81d1cd , < 2138480fceb654bec1845e691517ac409d0232c3
(git)
cpe:2.3:a:ash-project:ash_sqlite:*:*:*:*:*:*:*:* |
{
"containers": {
"cna": {
"affected": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ash-project:ash_sqlite:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshSqlite.SqlImplementation\u0027"
],
"packageName": "ash_sqlite",
"packageURL": "pkg:hex/ash_sqlite",
"product": "ash_sqlite",
"programFiles": [
"lib/sql_implementation.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshSqlite.SqlImplementation\u0027:do_get_path/6"
}
],
"repo": "https://github.com/ash-project/ash_sqlite",
"vendor": "ash-project",
"versions": [
{
"lessThan": "0.2.18",
"status": "affected",
"version": "0.1.2-rc.0",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ash-project:ash_sqlite:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshSqlite.SqlImplementation\u0027"
],
"packageName": "ash-project/ash_sqlite",
"packageURL": "pkg:github/ash-project/ash_sqlite",
"product": "ash_sqlite",
"programFiles": [
"lib/sql_implementation.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshSqlite.SqlImplementation\u0027:do_get_path/6"
}
],
"repo": "https://github.com/ash-project/ash_sqlite",
"vendor": "ash-project",
"versions": [
{
"lessThan": "2138480fceb654bec1845e691517ac409d0232c3",
"status": "affected",
"version": "c12be48a5b6295593199b0e445b70a4aef81d1cd",
"versionType": "git"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eAn application must let untrusted input reach a \u003ccode\u003eget_path/2\u003c/code\u003e path segment over a JSON/map column (for example a public calculation or filter argument that selects a key).\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "An application must let untrusted input reach a `get_path/2` path segment over a JSON/map column (for example a public calculation or filter argument that selects a key)."
}
],
"value": "An application must let untrusted input reach a get_path/2 path segment over a JSON/map column (for example a public calculation or filter argument that selects a key)."
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ash-project:ash_sqlite:*:*:*:*:*:*:*:*",
"versionEndExcluding": "0.2.18",
"versionStartIncluding": "0.1.2-rc.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Peter Ullrich"
},
{
"lang": "en",
"type": "reporter",
"value": "Peter Ullrich"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Zach Daniel / Ash Project"
},
{
"lang": "en",
"type": "coordinator",
"value": "Jonatan M\u00e4nnchen / EEF"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eImproper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sqlite allows an attacker who controls a \u003ccode\u003eget_path/2\u003c/code\u003e segment to traverse into nested JSON the application never exposed, disclosing private or \u003ccode\u003esensitive?\u003c/code\u003e embedded fields.\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eAshSqlite.SqlImplementation\u003c/code\u003e builds the SQLite \u003ccode\u003ejson_extract\u003c/code\u003e path with \u003ccode\u003e\"$.\" \u0026lt;\u0026gt; Enum.join(right, \".\")\u003c/code\u003e, so a single segment containing \u003ccode\u003e.\u003c/code\u003e, \u003ccode\u003e[\u003c/code\u003e, \u003ccode\u003e]\u003c/code\u003e, or \u003ccode\u003e$\u003c/code\u003e re-interprets the JSON path (for example \u003ccode\u003e\"private.secret\"\u003c/code\u003e 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 \u003ccode\u003eget_path\u003c/code\u003e segment (a common pick-a-field pattern) can read nested values it never meant to expose.\u003c/p\u003e\n\u003cp\u003eThis issue affects ash_sqlite: from 0.1.2-rc.0 before 0.2.18.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "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.\n\n`AshSqlite.SqlImplementation` builds the SQLite `json_extract` path with `\"$.\" \u003c\u003e 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.\n\nThis issue affects ash_sqlite: from 0.1.2-rc.0 before 0.2.18."
}
],
"value": "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.\n\nAshSqlite.SqlImplementation builds the SQLite json_extract path with \"$.\" \u003c\u003e 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.\n\nThis issue affects ash_sqlite: from 0.1.2-rc.0 before 0.2.18."
}
],
"impacts": [
{
"capecId": "CAPEC-676",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-676 NoSQL Injection"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "LOCAL",
"baseScore": 2.1,
"baseSeverity": "LOW",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-943",
"description": "CWE-943 Improper Neutralization of Special Elements in Data Query Logic",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-30T02:52:12.562Z",
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF"
},
"references": [
{
"tags": [
"vendor-advisory",
"related"
],
"url": "https://github.com/ash-project/ash_sqlite/security/advisories/GHSA-hrp2-5hgw-c83c"
},
{
"tags": [
"related"
],
"url": "https://cna.erlef.org/cves/CVE-2026-77846.html"
},
{
"tags": [
"related"
],
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-77846"
},
{
"tags": [
"patch"
],
"url": "https://github.com/ash-project/ash_sqlite/commit/2138480fceb654bec1845e691517ac409d0232c3"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "JSON path injection via unescaped get_path segments in AshSqlite"
}
},
"cveMetadata": {
"assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"assignerShortName": "EEF",
"cveId": "CVE-2026-77846",
"datePublished": "2026-08-30T02:52:12.562Z",
"dateReserved": "2026-08-30T02:15:01.493Z",
"dateUpdated": "2026-08-30T02:52:12.562Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-77846",
"date": "2026-08-30",
"epss": "0.00139",
"percentile": "0.03538"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-77846\",\"sourceIdentifier\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\",\"published\":\"2026-08-30T03:16:32.530\",\"lastModified\":\"2026-08-30T03:16:32.530\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.\\n\\nAshSqlite.SqlImplementation builds the SQLite json_extract path with \\\"$.\\\" \u003c\u003e 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.\\n\\nThis issue affects ash_sqlite: from 0.1.2-rc.0 before 0.2.18.\"}],\"affected\":[{\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\",\"affectedData\":[{\"vendor\":\"ash-project\",\"product\":\"ash_sqlite\",\"defaultStatus\":\"unaffected\",\"collectionURL\":\"https://repo.hex.pm\",\"packageName\":\"ash_sqlite\",\"cpes\":[\"cpe:2.3:a:ash-project:ash_sqlite:*:*:*:*:*:*:*:*\"],\"modules\":[\"\u0027Elixir.AshSqlite.SqlImplementation\u0027\"],\"programFiles\":[\"lib/sql_implementation.ex\"],\"programRoutines\":[{\"name\":\"\u0027Elixir.AshSqlite.SqlImplementation\u0027:do_get_path/6\"}],\"repo\":\"https://github.com/ash-project/ash_sqlite\",\"packageURL\":\"pkg:hex/ash_sqlite\",\"versions\":[{\"version\":\"0.1.2-rc.0\",\"lessThan\":\"0.2.18\",\"versionType\":\"semver\",\"status\":\"affected\"}]},{\"vendor\":\"ash-project\",\"product\":\"ash_sqlite\",\"defaultStatus\":\"unaffected\",\"collectionURL\":\"https://github.com\",\"packageName\":\"ash-project/ash_sqlite\",\"cpes\":[\"cpe:2.3:a:ash-project:ash_sqlite:*:*:*:*:*:*:*:*\"],\"modules\":[\"\u0027Elixir.AshSqlite.SqlImplementation\u0027\"],\"programFiles\":[\"lib/sql_implementation.ex\"],\"programRoutines\":[{\"name\":\"\u0027Elixir.AshSqlite.SqlImplementation\u0027:do_get_path/6\"}],\"repo\":\"https://github.com/ash-project/ash_sqlite\",\"packageURL\":\"pkg:github/ash-project/ash_sqlite\",\"versions\":[{\"version\":\"c12be48a5b6295593199b0e445b70a4aef81d1cd\",\"lessThan\":\"2138480fceb654bec1845e691517ac409d0232c3\",\"versionType\":\"git\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV40\":[{\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"4.0\",\"vectorString\":\"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X\",\"baseScore\":2.1,\"baseSeverity\":\"LOW\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"attackRequirements\":\"PRESENT\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"vulnConfidentialityImpact\":\"LOW\",\"vulnIntegrityImpact\":\"NONE\",\"vulnAvailabilityImpact\":\"NONE\",\"subConfidentialityImpact\":\"NONE\",\"subIntegrityImpact\":\"NONE\",\"subAvailabilityImpact\":\"NONE\",\"exploitMaturity\":\"NOT_DEFINED\",\"confidentialityRequirement\":\"NOT_DEFINED\",\"integrityRequirement\":\"NOT_DEFINED\",\"availabilityRequirement\":\"NOT_DEFINED\",\"modifiedAttackVector\":\"NOT_DEFINED\",\"modifiedAttackComplexity\":\"NOT_DEFINED\",\"modifiedAttackRequirements\":\"NOT_DEFINED\",\"modifiedPrivilegesRequired\":\"NOT_DEFINED\",\"modifiedUserInteraction\":\"NOT_DEFINED\",\"modifiedVulnConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedVulnIntegrityImpact\":\"NOT_DEFINED\",\"modifiedVulnAvailabilityImpact\":\"NOT_DEFINED\",\"modifiedSubConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedSubIntegrityImpact\":\"NOT_DEFINED\",\"modifiedSubAvailabilityImpact\":\"NOT_DEFINED\",\"Safety\":\"NOT_DEFINED\",\"Automatable\":\"NOT_DEFINED\",\"Recovery\":\"NOT_DEFINED\",\"valueDensity\":\"NOT_DEFINED\",\"vulnerabilityResponseEffort\":\"NOT_DEFINED\",\"providerUrgency\":\"NOT_DEFINED\"}}]},\"weaknesses\":[{\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-943\"}]}],\"references\":[{\"url\":\"https://cna.erlef.org/cves/CVE-2026-77846.html\",\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\"},{\"url\":\"https://github.com/ash-project/ash_sqlite/commit/2138480fceb654bec1845e691517ac409d0232c3\",\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\"},{\"url\":\"https://github.com/ash-project/ash_sqlite/security/advisories/GHSA-hrp2-5hgw-c83c\",\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\"},{\"url\":\"https://osv.dev/vulnerability/EEF-CVE-2026-77846\",\"source\":\"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\"}]}}"
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…