Skip to content
Threat Brief

← All advisories

CVE-2026-82759

Low 1.8No known exploitationFix available

Reversible IP address pseudonymisation in AshAuthentication audit log hash mode

Record last updated

CVSS score

1.8

Low on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.1%

Higher than 3% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-760

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
team-alembicash_authenticationfrom 4.12.0 before 4.15.04.15.0CVE Program
team-alembicash_authenticationfrom 5.0.0-rc.0 before 5.0.0-rc.145.0.0-rc.14CVE Program
team-alembicash_authentication255cfc9c0e511b7e0de39f8b3d676ae994fae06cNot documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references