CVE-2026-82759

Reversible IP address pseudonymisation in AshAuthentication audit log hash mode

LOW
1.8
CVSS Score
Published: September 17, 2026 at 01:08 PM UTC
Updated: September 18, 2026 at 06:29 PM UTC
1 product affected across 1 vendorAsh Authentication

Using ash_authentication by team-alembic?

Get instant alerts when new vulnerabilities affect ash_authentication - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW1.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

Use of a One-Way Hash with a Predictable Salt vulnerability in team-alembic AshAuthentication allows readers of the audit store to recover the client IP addresses that the audit log add-on's :hash privacy mode is meant to pseudonymise. AshAuthentication.AddOn.AuditLog.IpPrivacy.hash_ip/1 computes a single unkeyed :crypto.hash(:sha256, salt <> ip) and truncates the result to 16 hexadecimal characters. The salt is read from the :audit_log_ip_salt or :secret application config keys, and falls back to the constant "default-salt-change-in-production" published in the library source when neither is set, with nothing warning that the default is in use. The IPv4 space is only 2^32 values and SHA-256 is fast, so the whole hash table is precomputable and every stored value maps back to its source address. Truncating to 16 characters does not help, and even a configured salt leaves the hash cheap enough to enumerate once it leaks. 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.14.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.12.0 ≤ v < 4.15.05.0.0-rc.0 ≤ v < 5.0.0-rc.14255cfc9c0e511b7e0de39f8b3d676ae994fae06c4.12.05.0.0-rc.0
Affected range stops below 4.15.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.0.0-rc.14, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

1.8LOWEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-760

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card