Uncontrolled Resource Consumption vulnerability in ash-project ash allows an attacker to force an expensive regular expression to run on input that a length constraint should have already rejected.
Ash.Type.String.applyconstraints/2 (lib/ash/type/string.ex) evaluated the :match regex regardless of the minlength and max_length constraints on the same attribute. Because the length check did not gate the regex, an over-length value that the length constraint rejects still had the pattern applied to it, so the length limit that would otherwise bound the work never constrained the regex input. Against a backtracking pattern this yields catastrophic regex evaluation on attacker-sized input, and even a linear pattern runs on arbitrarily large input, consuming CPU per request. The fix skips the :match regex whenever a length constraint is violated, making the two checks order-independent.
This issue affects ash: from 0.10.0 before 3.32.2.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/82xxx/CVE-2026-82735.json",
"unresolved_ranges": [
{
"source": "AFFECTED_FIELD",
"extracted_events": [
{
"introduced": "0.10.0"
},
{
"fixed": "3.32.2"
},
{
"introduced": "05848d5f4affe60fddd812222a18ada080c0813b"
},
{
"fixed": "14928412a1a94a69c47df8e98920d3a2b09cdec4"
}
]
},
{
"source": "CPE_FIELD",
"extracted_events": [
{
"introduced": "0.10.0"
},
{
"fixed": "3.32.2"
}
]
},
{
"source": "DESCRIPTION",
"extracted_events": [
{
"introduced": "0.10.0"
},
{
"fixed": "3.32.2"
}
]
}
],
"cna_assigner": "EEF",
"cwe_ids": [
"CWE-400"
]
}