{"answers":{"affected":"1 open source package ship an affected version, including ash_paper_trail.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75847 exists.","fix":"Upgrade ash_paper_trail to 0.7.0 or later.","what":"CVE-2026-75847 is a medium-severity vulnerability in ash-project ash_paper_trail, 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-75847 and fix it if it is affected.\n\nWhat it is: CVE-2026-75847 is a medium-severity vulnerability in ash-project ash_paper_trail, 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-75847 exists.\n\nAffected packages and fixed versions:\n- ash_paper_trail (Hex): affected from 0.1.1; fixed in 0.7.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-75847/ (Markdown: https://insights.sbomify.com/CVE-2026-75847/index.md)","id":"CVE-2026-75847","markdown":"https://insights.sbomify.com/CVE-2026-75847/index.md","name":"CVE-2026-75847","record":{"aliases":["EEF-CVE-2026-75847","GHSA-wqjr-xmxp-j554"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir audit trail library","requires_auth":"none","summary":"Attackers with read access can recover plaintext sensitive attributes from version resources because sensitivity flags are incorrectly derived, exposing data in logs and outputs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Cleartext Storage of Sensitive Information vulnerability in ash-project ash_paper_trail allows an attacker with read access to the generated version resource to recover the plaintext of sensitive? attributes.\n\nAshPaperTrail stores the values of tracked sensitive? attributes in the generated version resource's changes map, which is declared public? true and sensitive? false, so the values are returned by the version resource's default read action and printed in logs, inspect output, and error messages instead of being redacted. AshPaperTrail.Resource.Transformers.CreateVersionResource derives the changes map's sensitivity from the ignore_attributes list (the attributes excluded from changes) rather than from the tracked attributes actually stored in it, and ignore_attributes defaults to empty, so the flag is effectively always false.\n\nThis issue affects ash_paper_trail: from 0.1.1 before 0.7.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":"Sensitive attribute values stored in a non-sensitive public changes map in AshPaperTrail","id":"CVE-2026-75847","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":"ArcadeDB before 26.8.1 Per-Type ACL Bypass via Batch Handlers","id":"CVE-2026-75850"},"packages":[{"ecosystem":"Hex","fixed":["0.7.0"],"introduced":["0.1.1"],"last_affected":[],"package":"ash_paper_trail","purl":"pkg:hex/ash_paper_trail","source":"EEF-CVE-2026-75847"}],"prev":{"headline":"ArcadeDB before 26.8.1 Unauthorized Function Deletion via DELETE FUNCTION","id":"CVE-2026-75846"},"products":["ash_paper_trail"],"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 with read access can recover plaintext sensitive attributes from version resources because sensitivity flags are incorrectly derived, exposing data in logs and outputs.","url":"https://insights.sbomify.com/CVE-2026-75847/"}