{"answers":{"affected":"1 open source package ship an affected version, including ash_authentication.","exploited":"There is no known exploitation of CVE-2026-82723 in the wild and no public exploit code.","fix":"Upgrade ash_authentication to a fixed version for your release line: 4.15.0 or 5.0.0-rc.2.","what":"CVE-2026-82723 is a low-severity vulnerability in team-alembic ash_authentication, published on 17 Sep 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-82723 and fix it if it is affected.\n\nWhat it is: CVE-2026-82723 is a low-severity vulnerability in team-alembic ash_authentication, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-82723 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ash_authentication (Hex): affected from 4.12.0; fixed in 4.15.0, 5.0.0-rc.2\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-82723/ (Markdown: https://insights.sbomify.com/CVE-2026-82723/index.md)","id":"CVE-2026-82723","markdown":"https://insights.sbomify.com/CVE-2026-82723/index.md","name":"CVE-2026-82723","record":{"aliases":["EEF-CVE-2026-82723","GHSA-59wx-q3r8-ghv4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Elixir authentication library","requires_auth":"high_privilege","summary":"Attackers with audit store access can retrieve password digests from logs, enabling offline password attacks against user accounts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":1.8,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Insertion of Sensitive Information into Log File vulnerability in team-alembic AshAuthentication allows disclosure of user password digests to readers of the audit store.\n\nThe audit_log add-on builds each entry's extra_data in AshAuthentication.AddOn.AuditLog.Auditor.build_extra_data/4, which takes :actor from the action callback context verbatim. Any audited action invoked with actor: set to a user record therefore deposits that record, including its hashed_password attribute, into the audit entry. The same module already collapses the audited identity to an opaque string via AshAuthentication.user_to_subject/1 and filters params against the strategy's configured allow-list, so the actor is the only stored value that reaches the audit store unfiltered. Marking the attribute sensitive?: true does not help, because that redacts inspect/1 output rather than JSON encoding or raw-term storage.\n\nThere is no attacker-controlled trigger and no network disclosure path: entries accumulate from ordinary authenticated activity, and an attacker's own requests deposit only their own digest. Exploitation requires independent read access to the audit store, such as database credentials, an audit role, a backup, or a log shipper, at which point the digests support offline password attack against every active account. Whether the material persists depends on the data layer, since raw-term stores keep it verbatim while a SQL store raises Protocol.UndefinedError and drops the entry unless the user resource derives Jason.Encoder.\n\nThis issue affects ash_authentication: from 4.12.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.2.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Actor record with password digest stored in AshAuthentication audit log entries","id":"CVE-2026-82723","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":6,"next":{"headline":"Broken access control in AshPhoenix SubdomainHook via a nil tenant in handle_subdomain","id":"CVE-2026-82724"},"packages":[{"ecosystem":"Hex","fixed":["4.15.0","5.0.0-rc.2"],"introduced":["4.12.0","5.0.0-rc.0"],"last_affected":[],"package":"ash_authentication","purl":"pkg:hex/ash_authentication","source":"EEF-CVE-2026-82723"}],"prev":{"headline":"AshAdmin LiveView events intern atoms from client input, exhausting the atom table (node DoS)","id":"CVE-2026-82722"},"products":["ash_authentication"],"published":"2026-09-17","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["team-alembic"]},"summary":"Attackers with audit store access can retrieve password digests from logs, enabling offline password attacks against user accounts.","url":"https://insights.sbomify.com/CVE-2026-82723/"}