CVE-2026-77950: CWE-209 Generation of Error Message Containing Sensitive Information in ash-project ash_typescript
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.
CVSS v4.0
Score 6.3medium
Affected software
ash-project
ash_typescript
ash-project
ash_typescript
cpe:2.3:a:ash-project:ash_typescript:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises in the apply_error_handler/3 function in lib/ash_typescript/rpc/errors.ex, which is responsible for redacting or suppressing errors before they reach the client. Error handlers are typically pattern-matching functions for expected error shapes. If an error shape is unmatched, a FunctionClauseError is raised, and the raw error map, including any sensitive data in variables, is returned to the client. Additionally, the rescue clause only catches exceptions, so errors that throw or exit still propagate unredacted. This behavior can inadvertently expose sensitive internal error details to unauthenticated attackers.
Potential Impact
An unauthenticated attacker can provoke errors that cause the system to return unredacted internal error data, potentially exposing sensitive information contained in error variables. This information disclosure can aid attackers in further reconnaissance or exploitation. The vulnerability does not require privileges or user interaction and has a low attack complexity, but the impact is limited to information disclosure without direct integrity or availability effects.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, developers should carefully implement error handlers to cover all expected error shapes and avoid returning raw error data. Avoid relying solely on pattern matching for error suppression and consider additional safeguards to prevent leaking sensitive information in error responses.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-30T17:30:01.402Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a963a79acd9273b491bc8c3
Added to database: 09/01/2026, 02:37:45 UTC
Last enriched: 09/07/2026, 14:50:58 UTC
Last updated: 10/14/2026, 06:48:20 UTC
Views: 87
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.