CVE-2026-82723: Actor record with password digest stored in AshAuthentication audit log entries
Noroxi assessment
Priority: Monitor (action score 7/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: team-alembic ash_authentication 17ea0dff3bad56a7e915e050c43ab7160b37901f, 4.15.0, 5.0.0-rc.2.
Low priority for now. Upgrade to team-alembic ash_authentication 17ea0dff3bad56a7e915e050c43ab7160b37901f, 4.15.0, 5.0.0-rc.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Sep 24, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-532
Report tools
Action score
7
Low priority for now.
- CVSS
- 7 / 40 · 1.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · EEF
- 1.8
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (EEF). Independent of NVD's CPE analysis and usually ahead of it.
team-alembic ash_authentication
- 4.12.0 and later · before 4.15.0affected · semver
- 5.0.0-rc.0 and later · before 5.0.0-rc.2affected · semver
- 255cfc9c0e511b7e0de39f8b3d676ae994fae06c and lateraffected · gitfixed in 17ea0dff3bad56a7e915e050c43ab7160b37901f, f6b49cc98b9ff7c16a1aeb12e35633a8d93a211f
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Hex | ash_authentication | from 4.12.0 · before 4.15.0 | 4.15.0 |
| Hex | ash_authentication | from 5.0.0-rc.0 · before 5.0.0-rc.2 | 5.0.0-rc.2 |
Same product
team-alembic: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-76949Remember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement36Monitor
- CVE-2026-91039dynamic_oidc identities are not namespaced by connection in ash_authentication, allowing cross-connection account takeover36Monitor
- CVE-2026-88952OAuth2 sign-in attached to an existing account without an email comparison in AshAuthentication36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-81637Sep 17, 2026 · Replayable OAuth2 CSRF state retained after a failed callback in AshAuthentication9Monitor
- ← EarlierCVE-2026-82685Sep 17, 2026 · Confirmation token accepted on any record in AshAuthentication30Monitor
- Later →CVE-2026-82759Sep 17, 2026 · Reversible IP address pseudonymisation in AshAuthentication audit log hash mode7Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| team-alembic ash_authentication | 17ea0dff3bad56a7e915e050c43ab7160b37901f | Vendor (CNA) |
| team-alembic ash_authentication | 4.15.0 | Vendor (CNA) |
| team-alembic ash_authentication | 5.0.0-rc.2 | Vendor (CNA) |
| team-alembic ash_authentication | f6b49cc98b9ff7c16a1aeb12e35633a8d93a211f | Vendor (CNA) |
| Hex:ash_authentication | 4.15.0 | Package registry (OSV) |
| Hex:ash_authentication | 5.0.0-rc.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- James Hartonremediation developer
- Peter Ullrichreporter
- Jonatan Männchen / EEFcoordinator
Not on record for this CVE: variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- cna.erlef.org/cves/CVE-2026-82723.html
- github.com/team-alembic/ash_authentication/commit/17ea0dff3bad56a7e915e050c43ab7160b37901f
- github.com/team-alembic/ash_authentication/commit/255cfc9c0e511b7e0de39f8b3d676ae994fae06c
- github.com/team-alembic/ash_authentication/commit/f6b49cc98b9ff7c16a1aeb12e35633a8d93a211f
- github.com/team-alembic/ash_authentication/security/advisories/GHSA-59wx-q3r8-ghv4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.