CVE-2026-81638
Improper Handling of Alternate Encoding vulnerability in …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- cna.erlef.org/cves/CVE-2026-81638.html
- github.com/ash-project/ash_double_entry/commit/d3e688d300a581ae214b3ca7d95ef4de63fbb050
- github.com/ash-project/ash_double_entry/security/advisories/GHSA-qxp2-vgp9-268q
- osv.dev/vulnerability/EEF-CVE-2026-81638
- github.com/ash-project/ash_double_entry/commit/1e5f7ce8ff25f519c904731a29eb1258324e561a
- nvd.nist.gov/vuln/detail/CVE-2026-81638
- cve.org/CVERecord?id=CVE-2026-81638
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.