Quick answers
- Is CVE-2026-77950 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77950 being exploited in the wild.
- How severe is CVE-2026-77950?
- Informational severity, published 1 September 2026.
- Which products and versions are affected?
- Ash-Project Ash Typescript 0.8.0 before 0.18.0.
- Is there a fix for CVE-2026-77950?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-77950 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77950?
- Check whether you run Ash-Project Ash Typescript at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an information disclosure flaw in the apply_error_handler/3 function in lib/ash_typescript/rpc/errors.ex. Error handlers are typically implemented as pattern-matching functions expecting specific error shapes; when an unmatched error shape is encountered, it raises FunctionClauseError, and the rescue clause logs a warning then returns the original untransformed error map—including any secrets in variables—to the client. The root cause is that the rescue catches exceptions only, not throws or exits, and pattern-matching failures in handlers become error publication vectors instead of suppression. An unauthenticated attacker can trigger this by sending a request that generates an unexpected error shape. The issue affects ash_typescript from version 0.8.0 before 0.18.0.
Affected products
- ash-project ash_typescript 0.8.0 before 0.18.0
Timeline
- 2026-09-01: disclosed