{"answers":{"affected":"1 open source package ship an affected version, including ash.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82752 exists.","fix":"Upgrade ash to 3.33.0 or later.","what":"CVE-2026-82752 is a medium-severity denial of service vulnerability in ash-project ash, published on 5 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82752 and fix it if it is affected.\n\nWhat it is: CVE-2026-82752 is a medium-severity denial of service vulnerability in ash-project ash, published on 5 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82752 exists.\n\nAffected packages and fixed versions:\n- ash (Hex): affected from 0.10.0; fixed in 3.33.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82752/ (Markdown: https://insights.sbomify.com/CVE-2026-82752/index.md)","id":"CVE-2026-82752","markdown":"https://insights.sbomify.com/CVE-2026-82752/index.md","name":"CVE-2026-82752","record":{"aliases":["EEF-CVE-2026-82752","GHSA-cwjv-574p-59f6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir Ash framework","requires_auth":"none","summary":"Attackers can bypass string length limits by using combining marks, causing unbounded storage growth and potential denial of service in applications using the Ash framework.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"Improper Validation of Specified Quantity in Input vulnerability in ash-project ash allows an attacker to store a value of arbitrary size in an attribute whose length constraint should bound it.\n\nAsh measures string length with Elixir's String.length/1, which counts Unicode graphemes, in the max_length and min_length constraints of Ash.Type.String (apply_constraints/2 in lib/ash/type/string.ex), in Ash.Resource.Validation.StringLength, and in the string_length expression function. A grapheme carries an unbounded number of combining marks, so a base character followed by a million combining acute accents is one grapheme and megabytes of data, and satisfies max_length: 2. Where the data layer imposes no independent limit (ETS, Mnesia, or a Postgres text column) the whole value is persisted, so an attacker can write an entire request body into an attribute declared with a small maximum and grow storage without bound.\n\nThe counting unit also disagrees with the storage layer, which counts codepoints rather than graphemes, so a value accepted by the constraint can still be rejected or truncated by the column. A Postgres varchar(n) column bounds the value itself and is not exposed.\n\nThis issue affects ash: from 0.10.0 before 3.33.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Ash string length constraints count graphemes, so a combining-mark string of any size passes max_length","id":"CVE-2026-82752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"Denial of service in ash authentication oauth2 server","id":"CVE-2026-82753"},"packages":[{"ecosystem":"Hex","fixed":["3.33.0"],"introduced":["0.10.0"],"last_affected":[],"package":"ash","purl":"pkg:hex/ash","source":"EEF-CVE-2026-82752"}],"prev":{"headline":"Unbounded key authorization in mpp Tempo fee-payer sponsorship inflates gas cost and sponsors access-key provisioning","id":"CVE-2026-82751"},"products":["ash"],"published":"2026-09-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["ash-project"]},"summary":"Attackers can bypass string length limits by using combining marks, causing unbounded storage growth and potential denial of service in applications using the Ash framework.","url":"https://insights.sbomify.com/CVE-2026-82752/"}