CVE-2026-82735: CWE-400 Uncontrolled Resource Consumption in ash-project ash
Description
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.apply_constraints/2 (lib/ash/type/string.ex) evaluated the :match regex regardless of the min_length 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.
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 in ash-project ash occurs in the Ash.Type.String.apply_constraints/2 function, where the :match regex is evaluated regardless of min_length and max_length constraints. This means that inputs exceeding length limits still undergo regex evaluation, which can be computationally expensive, especially with backtracking patterns, leading to uncontrolled resource consumption (CWE-400). The issue affects versions starting at 0.10.0 and before 3.32.2. The remediation is to skip the regex evaluation when length constraints are violated, making the checks order-independent and preventing excessive CPU usage.
Potential Impact
An attacker can supply input that exceeds length constraints but still triggers expensive regex evaluation, causing high CPU consumption per request. This can degrade system performance or lead to denial of service conditions due to resource exhaustion. The impact is limited to local attack vector with low attack complexity and no user interaction required, but it requires partial user privileges. There is no known exploitation in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix is to skip regex evaluation when length constraints are violated, but no official patch or vendor advisory is provided in the data. Monitor vendor channels for an official fix and apply it once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-31T00:59:10.001Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a964897acd9273b49296a83
Added to database: 09/01/2026, 03:37:59 UTC
Last enriched: 09/07/2026, 15:03:48 UTC
Last updated: 10/14/2026, 18:48:24 UTC
Views: 72
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.