Improper Input Validation vulnerability in ash-project ash_typescript allows a remote attacker to submit argument values outside a declared allowlist or bound on typed-controller routes.
AshTypescript.TypedController.RequestHandler in lib/ashtypescript/typedcontroller/requesthandler.ex calls Ash.Type.castinput/3 and treats an {:ok, cast} result as fully validated. In Ash these are separate steps: castinput/3 only coerces the term, while every constraint declared on the argument is applied by Ash.Type.applyconstraints/3, which this path never calls. Constraints such as oneof, maxlength, min and max, and match are therefore inert, so a value outside a declared allowlist is accepted and passed to the route handler. Codegen renders the same constraints into the generated TypeScript types, so an allowlist appears enforced to a TypeScript caller while any other HTTP client ignores it. Empty-string to nil normalization also lives in applyconstraints, so the allownil?: false check accepts "" for a required argument.
Where a constraint gates a role, a status, or a sort direction, this becomes a privilege or state-machine bypass.
This issue affects ash_typescript: from 0.15.0 before 0.18.0.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/82xxx/CVE-2026-82732.json",
"unresolved_ranges": [
{
"source": "AFFECTED_FIELD",
"extracted_events": [
{
"introduced": "546a15e1a2d7dbf1df2d5a6ee4404bc3da87852e"
},
{
"fixed": "21ab6f1229a4dccdb56bc37ed437d9672a0c4a4e"
}
]
}
],
"cna_assigner": "EEF",
"cwe_ids": [
"CWE-20"
]
}