Skip to content
Threat Brief

← All advisories

CVE-2026-77950

Medium 6.3No known exploitationFix available

RPC error handler fails open in AshTypescript, disclosing unredacted errors

Record last updated

CVSS score

6.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 36% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-209

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
ash-projectash_typescriptfrom 0.8.0 before 0.18.00.18.0CVE Program
ash-projectash_typescriptfrom cb01cc8749e5a2a17fb45aedbe75df30a9f1126e before 59d8e985a98cf2e01794dbe5b919b897a95311f459d8e985a98cf2e01794dbe5b919b897a95311f4CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references