Vulnerability EEF-CVE-2026-82759

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
2 months ago
September 17, 2026 at 01:08 PM UTC
Reversible IP address pseudonymisation in AshAuthentication audit log hash mode
4.12.0 - 5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13
4.12.0 - 5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13

Summary

Reversible IP address pseudonymisation in AshAuthentication audit log hash mode

Details

Summary

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.

Configurations

Only applications that enable the audit_log add-on and set its ip_privacy mode to :hash store the affected value. Other modes (:none, :truncate, :exclude) do not reach hash_ip/1.

The complete break additionally requires the default salt, that is neither :audit_log_ip_salt nor :secret configured under the :ash_authentication application. This is the out-of-the-box state: no warning or error is raised when the hardcoded salt is in use.

Related Vulnerabilities

Other vulnerabilities affecting the same packages

Unknown
18 days ago
AshAuthentication log_out_everywhere leaves sessions valid after a password reset or non-atomic password change
4.5.0 - 4.8.3 and 4.8.5 - 5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 and 5.0.0-rc.14 and 5.0.0-rc.15 EEF-CVE-2026-110826
4.5.0 - 4.8.3 and 4.8.5 - 5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 and 5.0.0-rc.14 and 5.0.0-rc.15 EEF-CVE-2026-110826
Unknown
18 days ago
AshAuthentication brute_force_strategy does not limit sign-in and request actions defined on the resource
5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 and 5.0.0-rc.14 and 5.0.0-rc.15 EEF-CVE-2026-118505
5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 and 5.0.0-rc.14 and 5.0.0-rc.15 EEF-CVE-2026-118505
Unknown
18 days ago
AshAuthentication TOTP setup lets a user install their own authenticator secret on another user's account
5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 and 5.0.0-rc.14 and 5.0.0-rc.15 EEF-CVE-2026-119215
5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 and 5.0.0-rc.14 and 5.0.0-rc.15 EEF-CVE-2026-119215
Unknown
2 months ago
Session id is not renewed on authentication in ash_authentication, allowing session fixation
3.0.3 - 3.3.1 and 3.5.0 - 3.7.6 and 3.7.8 - 4.0.0-rc.0 and 4.0.0-rc.1 and 4.0.0-rc.2 and 4.0.0-rc.3 and 4.0.0-rc.5 and 4.0.0-rc.6 and 4.0.0 - 4.8.3 and 4.8.5 - 5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 EEF-CVE-2026-86688
3.0.3 - 3.3.1 and 3.5.0 - 3.7.6 and 3.7.8 - 4.0.0-rc.0 and 4.0.0-rc.1 and 4.0.0-rc.2 and 4.0.0-rc.3 and 4.0.0-rc.5 and 4.0.0-rc.6 and 4.0.0 - 4.8.3 and 4.8.5 - 5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 EEF-CVE-2026-86688
Unknown
2 months ago
Remember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement
4.10.0 - 5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 EEF-CVE-2026-76949
4.10.0 - 5.0.0-rc.0 and 5.0.0-rc.1 and 5.0.0-rc.2 and 5.0.0-rc.3 and 5.0.0-rc.4 and 5.0.0-rc.5 and 5.0.0-rc.6 and 5.0.0-rc.7 and 5.0.0-rc.8 and 5.0.0-rc.9 and 5.0.0-rc.10 and 5.0.0-rc.11 and 5.0.0-rc.12 and 5.0.0-rc.13 EEF-CVE-2026-76949
View all vulnerabilities for these packages

Impacted packages

Timeline

Published
2 months ago
September 17, 2026 at 01:08 PM UTC
Fixed (5.0.0-rc.14)
2 months ago
September 17, 2026 at 12:03 AM UTC
Fixed (4.15.0)
2 months ago
September 17, 2026 at 12:14 AM UTC
Last Modified
2 days ago
November 20, 2026 at 06:15 AM UTC