Answer in brief
CVE-2026-77950 records a Unknown severity vulnerability in RPC error handler fails open in AshTypescript, disclosing unredacted errors. The current sources do not mark it as known exploited. The current feed maps 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.
A CVSS score is not reported in the current record. 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_typescript (generic), ash-project/ash_typescript (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash_typescriptgeneric | >=0.8.0 <0.18.0 | 0.18.0 |
| ash-project/ash_typescriptgeneric | >=cb01cc8749e5a2a17fb45aedbe75df30a9f1126e <59d8e985a98cf2e01794dbe5b919b897a95311f4 | 59d8e985a98cf2e01794dbe5b919b897a95311f4 |
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 receive unredacted internal error data by provoking an error shape the configured error handler does not match. apply_error_handler/3 in lib/ash_typescript/rpc/errors.ex is the only hook an application has for redacting or suppressing errors before they reach the client, with a nil return dropping the error entirely. Its rescue clause logs a warning and then returns the original, pre-handler error map. Error handlers are conventionally written as pattern-matching functions over expected error shapes, so an unmatched shape raises FunctionClauseError and the raw transformed error, including any secrets carried in vars, is emitted instead. An intent to suppress an error becomes an intent to publish it. The rescue catches exceptions only, so a handler that throws or exits still propagates. This issue affects ash_typescript: from 0.8.0 before 0.18.0.
Quoted source text, attributed separately from HOL analysis.