Vulnerability EEF-CVE-2026-81638

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
2 months ago
September 07, 2026 at 10:33 PM UTC
Non-canonical ULID spellings are accepted and alias to the same record in ash_double_entry
0.1.0 - 1.0.0-rc.0 and 1.0.0 - 1.0.18
0.1.0 - 1.0.0-rc.0 and 1.0.0 - 1.0.18

Summary

Non-canonical ULID spellings are accepted and alias to the same record in ash_double_entry

Details

Summary

Improper Handling of Alternate Encoding vulnerability in ash-project ash_double_entry allows an attacker to submit several distinct string spellings of the same identifier.

AshDoubleEntry.ULID renders a 128-bit ULID as 26 Crockford base-32 characters, but the first character encodes only 3 bits, so canonical values are 0 to 7. decode/1 in lib/ulid.ex masks the first character to its low 3 bits and valid?/1 accepts all 32 characters in that position, so 0..., 8..., G... and R... decode to the identical 16-byte value and resolve to the same row. When the type is exposed as a public ID over an HTTP or API boundary, an attacker-supplied ID can be spelled differently from the record it actually reads or writes, desynchronizing or bypassing string-level checks such as idempotency and deduplication keys, deny-lists, audit correlation, or signatures computed over the submitted ID.

This issue affects ash_double_entry: from 0.1.0 before 1.0.19.

Configurations

Reachable only when an application exposes AshDoubleEntry.ULID as a public identifier over an HTTP or API boundary and performs string-level checks on the submitted ID (idempotency or deduplication keys, deny-lists, audit correlation, or signatures) rather than treating the value as opaque.

Impacted packages

Timeline

Published
2 months ago
September 07, 2026 at 10:33 PM UTC
Fixed (1.0.19)
2 months ago
September 07, 2026 at 08:24 PM UTC
Last Modified
2 days ago
November 20, 2026 at 06:01 AM UTC