{"answers":{"affected":"1 open source package ship an affected version, including ash_sqlite.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77846 exists.","fix":"Upgrade ash_sqlite to 0.2.18 or later.","what":"CVE-2026-77846 is a low-severity vulnerability in ash-project ash_sqlite, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77846 and fix it if it is affected.\n\nWhat it is: CVE-2026-77846 is a low-severity vulnerability in ash-project ash_sqlite, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77846 exists.\n\nAffected packages and fixed versions:\n- ash_sqlite (Hex): affected from 0.1.2-rc.0; fixed in 0.2.18\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77846/ (Markdown: https://insights.sbomify.com/CVE-2026-77846/index.md)","id":"CVE-2026-77846","markdown":"https://insights.sbomify.com/CVE-2026-77846/index.md","name":"CVE-2026-77846","record":{"aliases":["EEF-CVE-2026-77846","GHSA-hrp2-5hgw-c83c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir SQLite library","requires_auth":"none","summary":"Attackers can read private nested JSON fields by injecting special characters into path segments, exposing sensitive data in AshSqlite applications.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"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"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"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.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"JSON path injection via unescaped get_path segments in AshSqlite","id":"CVE-2026-77846","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Tycon Systems TPDIN-Monitor-WEB3 Use of Hard-coded Credentials","id":"CVE-2026-77847"},"packages":[{"ecosystem":"Hex","fixed":["0.2.18"],"introduced":["0.1.2-rc.0"],"last_affected":[],"package":"ash_sqlite","purl":"pkg:hex/ash_sqlite","source":"EEF-CVE-2026-77846"}],"prev":{"headline":"Cross-site scripting in SOY Calendar","id":"CVE-2026-77838"},"products":["ash_sqlite"],"published":"2026-08-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["ash-project"]},"summary":"Attackers can read private nested JSON fields by injecting special characters into path segments, exposing sensitive data in AshSqlite applications.","url":"https://insights.sbomify.com/CVE-2026-77846/"}