# 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.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** EEF-CVE-2026-82733, GHSA-ghhw-qh7p-55xr

## 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 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-82733?

1 open source package ship an affected version, including ash_typescript.


| Package | Ecosystem | 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82733 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82733 exists.

Affected packages and fixed versions:
- ash_typescript (Hex): affected from 0.15.0; fixed in 0.18.0

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82733/ (Markdown: https://insights.sbomify.com/CVE-2026-82733/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82733
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82733
- OSV: https://osv.dev/vulnerability/CVE-2026-82733

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82733/
Summaries are generated and may contain mistakes; the official description above is the record.