CVE-2026-82738: CWE-20 Improper Input Validation in ash-project ash
Description
Improper Input Validation vulnerability in ash-project ash allows an attacker to persistently deny reads of a record by storing a non-version-7 UUID in an Ash.Type.UUIDv7 attribute. Ash.Type.UUIDv7.cast_input/2 accepts any well-formed UUID string, including non-version-7 UUIDs, and stores it as a 16-byte binary. On read, cast_stored/2 (lib/ash/type/uuid_v7.ex) routes the stored binary back through cast_input/2, which since an input-validation tightening in v3.6.3 matches only version-7 (and optionally version-4) 16-byte binaries and otherwise expects a 36-character string. A stored non-v7 16-byte binary matches neither clause and returns :error, so every later read of that record fails. An attacker able to set such an attribute poisons the row permanently. The fix decodes any 16-byte stored binary directly in cast_stored/2. This issue affects ash: from 3.6.3 before 3.32.2.
CVSS v4.0
Score 5.9medium
Affected software
ash-project
ash
ash-project
ash
cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because Ash.Type.UUIDv7.cast_input/2 accepts any well-formed UUID string, including non-version-7 UUIDs, and stores it as a 16-byte binary. On reading, cast_stored/2 routes the stored binary back through cast_input/2, which since version 3.6.3 only matches version-7 (and optionally version-4) UUID binaries or expects a 36-character string. A stored non-version-7 16-byte binary matches neither condition and returns :error, causing all subsequent reads of that record to fail. An attacker who can set such an attribute can poison the row permanently. The fix involves decoding any 16-byte stored binary directly in cast_stored/2.
Potential Impact
An attacker able to store a non-version-7 UUID in an Ash.Type.UUIDv7 attribute can cause persistent denial of read access to that record, effectively poisoning the data and causing failures on all subsequent reads of the affected record. This impacts data availability for the poisoned records.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary fix information is provided in the available data. Users should monitor vendor communications for updates and apply any official patches once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-31T00:59:10.002Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a964897acd9273b49296a89
Added to database: 09/01/2026, 03:37:59 UTC
Last enriched: 09/07/2026, 15:05:33 UTC
Last updated: 10/14/2026, 18:48:24 UTC
Views: 67
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.