{"answers":{"affected":"1 open source package ship an affected version, including ash_graphql.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78693 exists.","fix":"Upgrade ash_graphql to 1.11.0 or later.","what":"CVE-2026-78693 is a medium-severity vulnerability in ash-project ash_graphql, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-78693 and fix it if it is affected.\n\nWhat it is: CVE-2026-78693 is a medium-severity vulnerability in ash-project ash_graphql, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78693 exists.\n\nAffected packages and fixed versions:\n- ash_graphql (Hex): affected from 1.9.0; fixed in 1.11.0\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-78693/ (Markdown: https://insights.sbomify.com/CVE-2026-78693/index.md)","id":"CVE-2026-78693","markdown":"https://insights.sbomify.com/CVE-2026-78693/index.md","name":"CVE-2026-78693","record":{"aliases":["EEF-CVE-2026-78693","GHSA-ppr2-g9h8-w7qp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Elixir GraphQL library","requires_auth":"none","summary":"Remote attackers can read internal field names in GraphQL errors if custom error handlers are used, bypassing intended redaction mechanisms.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_graphql allows a remote client to read internal field names that an application configured its error_handler to redact.\n\nIn AshGraphql.Errors, each error is passed to the configured error_handler and the returned map is merged with the pre-handler path via Map.put_new(handled, :path, path). Because put_new defers to the handler only when the handler itself set :path, a sanitizing handler that returns a fresh map or deletes :path has that decision reverted. The re-injected path comes from build_error_path/5, which falls back to raw internal Ash attribute and argument names when no field_names mapping is configured. A validation failure on a non-exposed or nested field therefore returns internal names in the GraphQL error path, defeating the application's redaction.\n\nThis issue affects ash_graphql: from 1.9.0 before 1.11.0.","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":"Incomplete redaction re-attaches the original error path in AshGraphql, leaking internal field names","id":"CVE-2026-78693","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":"rename_tenant returns :ok on a failed rename, enabling cross-tenant access in AshPostgres","id":"CVE-2026-78699"},"packages":[{"ecosystem":"Hex","fixed":["1.11.0"],"introduced":["1.9.0"],"last_affected":[],"package":"ash_graphql","purl":"pkg:hex/ash_graphql","source":"EEF-CVE-2026-78693"}],"prev":{"headline":"Unescaped backslash allows LIKE wildcard injection in AshSql string search","id":"CVE-2026-78691"},"products":["ash_graphql"],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["ash-project"]},"summary":"Remote attackers can read internal field names in GraphQL errors if custom error handlers are used, bypassing intended redaction mechanisms.","url":"https://insights.sbomify.com/CVE-2026-78693/"}