{"answers":{"affected":"1 open source package ship an affected version, including ash_double_entry.","exploited":"There is no known exploitation of CVE-2026-81638 in the wild and no public exploit code.","fix":"Upgrade ash_double_entry to 1.0.19 or later.","what":"CVE-2026-81638 is a low-severity vulnerability in ash-project ash_double_entry, published on 7 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81638 and fix it if it is affected.\n\nWhat it is: CVE-2026-81638 is a low-severity vulnerability in ash-project ash_double_entry, published on 7 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81638 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ash_double_entry (Hex): affected from 0.1.0; fixed in 1.0.19\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81638/ (Markdown: https://insights.sbomify.com/CVE-2026-81638/index.md)","id":"CVE-2026-81638","markdown":"https://insights.sbomify.com/CVE-2026-81638/index.md","name":"CVE-2026-81638","record":{"aliases":["EEF-CVE-2026-81638","GHSA-qxp2-vgp9-268q"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir ULID library","requires_auth":"none","summary":"Attackers can bypass string-based security checks like idempotency or deny-lists by using non-canonical ULID spellings that resolve to the same record.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-173","name":"Improper Handling of Alternate Encoding"}],"description":"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.\n\nAshDoubleEntry.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.\n\nThis issue affects ash_double_entry: from 0.1.0 before 1.0.19.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Non-canonical ULID spellings are accepted and alias to the same record in ash_double_entry","id":"CVE-2026-81638","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"other","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Softish C6 Ear Camera and EarVision Android Application Use of Hard-coded Credentials","id":"CVE-2026-81640"},"packages":[{"ecosystem":"Hex","fixed":["1.0.19"],"introduced":["0.1.0"],"last_affected":[],"package":"ash_double_entry","purl":"pkg:hex/ash_double_entry","source":"EEF-CVE-2026-81638"}],"prev":{"headline":"Replayable OAuth2 CSRF state retained after a failed callback in AshAuthentication","id":"CVE-2026-81637"},"products":["ash_double_entry"],"published":"2026-09-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["ash-project"]},"summary":"Attackers can bypass string-based security checks like idempotency or deny-lists by using non-canonical ULID spellings that resolve to the same record.","url":"https://insights.sbomify.com/CVE-2026-81638/"}