ash-project ash up to 3.32.1 String Type Constraints lib/ash/type/string.ex Ash.Type.String.apply_constraints resource consumption

Summaryinfo

A vulnerability, which was classified as problematic, has been found in ash-project ash up to 3.32.1. Affected is the function Ash.Type.String.apply_constraints of the file lib/ash/type/string.ex of the component String Type Constraints. The manipulation leads to resource consumption. This vulnerability is uniquely identified as CVE-2026-82735. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in ash-project ash up to 3.32.1 and classified as problematic. This issue affects the function Ash.Type.String.apply_constraints of the file lib/ash/type/string.ex of the component String Type Constraints. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-82735 since 08/31/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 3.32.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Project Management Software

Vendor

• ash-project

Name

• ash

Version

• 3.32.0
• 3.32.1

Website

• Product: https://github.com/ash-project/ash/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion