Storage exhaustion via grapheme-based length validation
Published Sep 5, 2026 · Updated Sep 8, 2026
Improper quantity validation in Ash Framework Ash before 3.33.0 allows attackers to persist oversized strings through constrained attributes. String.length/1 counts an unbounded run of Unicode combining marks as one grapheme, so Ash length checks accept values far larger than their declared limit. Exposure requires client-controlled input, a length-constrained attribute, and ETS, Mnesia, or PostgreSQL text storage; repeated writes can exhaust storage.
Summary
What happened
Improper quantity validation in Ash Framework Ash before 3.33.0 allows attackers to persist oversized strings through constrained attributes. String.length/1 counts an unbounded run of Unicode combining marks as one grapheme, so Ash length checks accept values far larger than their declared limit. Exposure requires client-controlled input, a length-constrained attribute, and ETS, Mnesia, or PostgreSQL text storage; repeated writes can exhaust storage.
The record
- CVE
- CVE-2026-82752
- Published
- Sep 5, 2026
- Updated
- Sep 8, 2026
- Vendor
- Ash Framework
- Product
- Ash
- Classifications
- CWE-1284, CAPEC-153, T1499.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.10.0 <3.33.0
- Affected versionversion=05848d5f4affe60fddd812222a18ada080c0813b <* changes=[{"at":"a64cab49b8886503e6b7c7b211d83c475aac48ca","status":"unaffected"},{"at":"cdbf4c4da6bda5f6f139078f01a64320b595216d","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Ash combining-mark storage exhaustion proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo