Skip to content
Connect AISign inSign up free
CVE-2026-816382.1LowCWE-173

CVE-2026-81638: Non-canonical ULID spellings are accepted and alias to the same record in ash_double_entry

ash-project · ash_double_entry

Fixed in 1.0.19 · Affected: ash-project ash_double_entry before 1.0.19 · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.2%probability of exploitation in the next 30 days
8th percentile
050100

Higher than 8% of scored CVEs

2.1LowCVSS 4.0
Low

DescriptionCVE.org

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.

Affected products2

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • ash-project · ash_double_entryfrom 0.1.0 before 1.0.19
  • ash-project · ash_double_entryVersions not stated

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template

CoverageNo articles yet

No CyberSIXT article names CVE-2026-81638 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References