CVE-2026-82733 Route handler return value echoed into AshTypescript error response
An unauthenticated attacker can read sensitive internal application data, including hashed passwords and tokens, from HTTP 500 error responses.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-82733?
CVE-2026-82733 is a medium-severity vulnerability in ash-project ash_typescript, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_typescript allows an unauthenticated attacker to read internal application data from an HTTP 500 response body.
When a typed-controller route handler returns anything other than a %Plug.Conn{}, dispatch/3 in lib/ash_typescript/typed_controller/request_handler.ex passes the value to unexpected_return/2, which interpolates inspect(value, limit: 50) directly into the response message. The limit option bounds elements per collection rather than the term as a whole, so a handler falling through with a term such as {:error, %User{}} or a changeset serialises its full field set, including hashed passwords, tokens, and tenant identifiers, into the JSON error returned to the caller.
This contradicts the module's own posture elsewhere: the rescue clause gates Exception.message/1 behind AshTypescript.typed_controller_show_raised_errors?/0 and otherwise returns a generic message, while this path is ungated and always echoes.
This issue affects ash_typescript: from 0.15.0 before 0.18.0.
Weakness: CWE-209
Which versions are affected by CVE-2026-82733?
1 open source package ship an affected version, including ash_typescript.
| Package | Affected | Fixed in |
|---|---|---|
ash_typescript Hex | From 0.15.0 | 0.18.0 |
How do I fix CVE-2026-82733?
Upgrade ash_typescript to 0.18.0 or later.
Is CVE-2026-82733 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82733 exists.
Sources
Also known as EEF-CVE-2026-82733, GHSA-ghhw-qh7p-55xr.