Vulnerabilities

Vulnerability · CVE-2026-105283

Internal error terms inspected into AshTypescript RPC error responses

Published Oct 12, 2026 · catalog updated Oct 12, 2026 · Internal error terms inspected

Check if you run it

No confirmed exploitation is on record for CVE-2026-105283. EPSS is 0.32%. Act only if a listed version of Internal error terms inspected is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Internal error terms inspected).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.32%
Remediation
Advisory link
Affected products
Hex ash_typescript

## Summary Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_typescript allows an unauthenticated attacker to read internal Elixir terms from an RPC error response by provoking an error the error builder has no dedicated clause for. in renders a pipeline error term that matches no specific clause with and places the result in of the client-facing error. Ash exceptions take a separate path in where unhandled cases are redacted behind an , but these fallbacks have no redaction, so whatever the term carries reaches the HTTP or channel response. Two request paths hand it such terms: a struct-typed action argument with an invalid nested value, where in throws the raw cast error into the builder, and field selection on a generic action that returns a primitive, where inspects the full struct into . Resource module names in are not treated as sensitive and are out of scope. This issue affects ash_typescript: from 0.1.0 before 0.19.1. ## Details **1. Error funnel.** runs the request through , and . Any from these goes to , which calls with the raw reason term. **2. Unredacted fallbacks.** has clauses for the error tuples the pipeline is expected to emit. A two-tuple whose first element is an atom but matches no clause is rendered as with set to , and any other term becomes with set to . Ash exceptions never reach these clauses because handles them and redacts unhandled ones behind an , so only this path has no redaction. **3. Reachable triggers.** throws the raw error, a keyword list, when a struct-typed argument fails to cast, and turns the throw into for the funnel. Separately, requesting on a generic action whose return type is a primitive produces an tuple whose is formatted by , which inspects the whole struct, constraints and decoration included, into . ## Proof of concept 1. Expose an AshTypescript RPC action that takes a struct-typed argument, for example an argument whose struct has a UUID field. 2. Send the action reques

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Hex ash_typescript0.1.0 → 0.19.1

How to fix CVE-2026-105283

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-105283. EPSS is 0.32%. Act only if a listed version of Internal error terms inspected is installed.

Which versions are affected?

Compare what you have installed with 0.1.0 → 0.19.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-209. EPSS 0.32%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 12, 2026 · GitHub Advisory Database

    Detected

    ## Summary Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_typescript allows an unauthenticated attacker to read internal Elixir terms from an RPC error response by provoking an error the error builder has no dedicated clause for. in renders a pipeline error term that matches no specific clause with and places the result in of the client-facing error.

  2. Oct 12, 2026 · GitHub Advisory Database

    Fix available

    ash_typescript fixed in 0.19.1

  3. Oct 12, 2026 · GitHub Advisory Database

    Fix available

    ash_typescript fixed in 0.19.1

  4. Oct 12, 2026 · GitHub Advisory Database

    Updated

    ## Summary Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_typescript allows an unauthenticated attacker to read internal Elixir terms from an RPC error response by provoking an error the error builder has no dedicated clause for. in renders a pipeline error term that matches no specific clause with and places the result in of the client-facing error.

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.