Answer in brief
CVE-2026-82733 records a Medium severity (CVSS 6.3) vulnerability in Route handler return value echoed into AshTypescript error response. The current sources do not mark it as known exploited. The current feed maps ash-project/ash-project/ash_typescript (generic), ash-project/ash_typescript (generic), ash-project/ash_typescript (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash-project/ash-project/ash_typescript (generic), ash-project/ash_typescript (generic), ash-project/ash_typescript (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash-project/ash_typescriptgeneric | >=546a15e1a2d7dbf1df2d5a6ee4404bc3da87852e <dec80e29543f96e43eeece8501376562f17ac638 | dec80e29543f96e43eeece8501376562f17ac638 |
| ash-project/ash_typescriptgeneric | >=546a15e1a2d7dbf1df2d5a6ee4404bc3da87852e <dec80e29543f96e43eeece8501376562f17ac638 | dec80e29543f96e43eeece8501376562f17ac638 |
| ash-project/ash_typescriptgeneric | >=0.15.0 <0.18.0 | 0.18.0 |
Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.