Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-209 (通过错误消息导致的信息暴露) — Vulnerability Class 395

395 vulnerabilities classified as CWE-209 (通过错误消息导致的信息暴露). AI Chinese analysis included.

CWE-209 represents a critical information disclosure weakness where software inadvertently exposes sensitive internal details through error messages. This flaw typically occurs when applications return verbose stack traces, database paths, or user-specific data to end-users during failure states. Attackers exploit this by triggering specific errors to gather reconnaissance information, such as server architecture, file structures, or valid user identifiers, which facilitates further targeted attacks like SQL injection or privilege escalation. To mitigate this risk, developers must implement robust error handling mechanisms that separate internal diagnostic logs from user-facing messages. By standardizing generic, non-descriptive error responses for external users while retaining detailed logs for internal debugging, organizations can prevent attackers from leveraging error output to map system vulnerabilities or compromise sensitive data integrity.

MITRE CWE Description
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Common Consequences (1)
Confidentiality Read Application Data
Often this will either reveal sensitive information which may be used to launch another, more focused attack or disclose private information stored in the server. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application. In tur…
Mitigations (5)
Implementation Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or…
Implementation Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
Effectiveness: Defense in Depth
Implementation, Build and Compilation Debugging information should not make its way into a production release.
Implementation, Build and Compilation Debugging information should not make its way into a production release.
Examples (2)
In the following example, sensitive information might be printed depending on the exception that occurs.
try { /.../ } catch (Exception e) { System.out.println(e); }
Bad · Java
This code tries to open a database connection, and prints any exceptions that occur.
try { openDbConnection(); } //print exception message that includes exception message and configuration file location catch (Exception $e) { echo 'Caught exception: ', $e->getMessage(), '\n'; echo 'Check credentials in config file at: ', $Mysql_config_location, '\n'; }
Bad · PHP
CVE ID Title CVSS Severity Published
CVE-2026-84499 Automation-controller: automation-controller-container: automation-controller: write-only survey password recovered in plaintext via schedule/workflowjobtemplatenode survey min/max validation error message — Red Hat Ansible Automation Platform 2.5 for RHEL 8 7.7 High 2026-09-23
CVE-2026-71463 Automation-controller: automation-controller-container: automation-controller: notification template jinja whitelist bypass via conditional gating leaks tracebacks — Red Hat Ansible Automation Platform 2.5 for RHEL 8 2.7 Low 2026-09-23
CVE-2026-71461 Automation-controller: automation-controller-container: automation-controller: verbose internal exception disclosure via hostlist bare-exception handler — Red Hat Ansible Automation Platform 2.7 4.3 Medium 2026-09-23
CVE-2026-4921 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 2.7 Low 2026-09-23
CVE-2026-3626 Multiple Vulnerabilities in IBM Concert Software — Concert 5.3 Medium 2026-09-23
CVE-2026-85709 LightRAG: Sensitive Information Exposure Through Raw Exception Messages in API Error Responses — LightRAG 5.3 Medium 2026-09-22
CVE-2026-1030 Multiple vulnerabilities affect IBM License Key Server Administration and Reporting Tool and IBM LKS Administration Agent — Common Licensing 4.3 Medium 2026-09-18
CVE-2025-1350 Multiple vulnerabilities in IBM Controller — Controller 5.3 Medium 2026-09-18
CVE-2026-92936 vm2 3.11.0 before 3.11.7 Information Disclosure via Error Stack — vm2 5.8 Medium 2026-09-17
CVE-2026-55375 canto-saas-api: OAuth credentials exposed in URL query string and exception messages — canto-saas-api 5.3 Medium 2026-09-15
CVE-2026-55102 hashi-vault-js: Vault token and secret values exposed in thrown errors — hashi-vault-js 5.8 Medium 2026-09-14
CVE-2026-66306 Skype for Business Information Disclosure Vulnerability — Skype for Business Server 2015 CU13 6.5 Medium 2026-09-08
CVE-2026-69294 Microsoft COM for Windows Information Disclosure Vulnerability — Windows 10 Version 1809 5.5 Medium 2026-09-08
CVE-2026-67383 Microsoft SQL Server Information Disclosure Vulnerability — Microsoft SQL Server 2025 (CU8) 6.5 Medium 2026-09-08
CVE-2026-69684 Windows Error Reporting Information Disclosure Vulnerability — Windows 10 Version 1607 5.5 Medium 2026-09-08
CVE-2026-69552 Windows Print Spooler Components Information Disclosure Vulnerability — Windows 10 Version 1607 5.7 Medium 2026-09-08
CVE-2026-11873 Pki-core: dogtag-pki: empty request to dogtag /ca/rest/certrequests causes http 500, java exception, and stacktrace disclosure — Red Hat Certificate System 9 6.5 Medium 2026-09-01
CVE-2026-82739 Ash.Resource.Validation.Confirm leaks a confirmed field's stored value in the atomic mismatch error — ash 2.1 Low 2026-09-01
CVE-2026-82733 Route handler return value echoed into AshTypescript error response — ash_typescript 6.3 Medium 2026-09-01
CVE-2026-77950 RPC error handler fails open in AshTypescript, disclosing unredacted errors — ash_typescript 6.3 Medium 2026-09-01
CVE-2026-82727 AshPhoenix Form.Auto leaks submitted params in an unknown _union_type error message — ash_phoenix 2.3 Low 2026-08-31
CVE-2026-75760 AshAi vectorize change leaks raw embedding-provider errors, including credentials, in a user-facing error — ash_ai 7.1 High 2026-08-31
CVE-2026-82580 AshAi echoes raw tool exception messages into the conversation, disclosing internal details — ash_ai 5.3 Medium 2026-08-31
CVE-2026-78693 Incomplete redaction re-attaches the original error path in AshGraphql, leaking internal field names — ash_graphql 6.9 Medium 2026-08-30
CVE-2026-21809 HCL BigFix Quantum Risk Analyzer is affected by generating error messages with sensitive information — BigFix Quantum Risk Analyzer 3.9 Low 2026-08-26
CVE-2026-79777 rclone before v1.75.0 Information Disclosure via RC API — rclone 2.7 Low 2026-08-25
CVE-2026-8173 Information Disclosure via 'Copy learned MAC Addresses' Function — Xelity 4TX M GE 5.3 Medium 2026-08-24
CVE-2026-33333 Combodo iTop: Information disclosure in ajax.render.php — iTop 3.5 Low 2026-08-21
CVE-2026-77076 n8n before 1.123.69 Credential Leak via GraphQL Node Error — n8n 7.1 High 2026-08-20
CVE-2026-53458 Blueprint Studio API exposed internal exception details — blueprint-studio 5.3 Medium 2026-08-18

Vulnerabilities classified as CWE-209 (通过错误消息导致的信息暴露) represent 395 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.