What is CWE-200?
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include: private, personal information, such as personal messages, financial data, health records, geographic location, or contact details system status and environment, such as the operating system and installed packages business secrets and intellectual property network status and configuration the product's own code or internal state metadata, e.g. logging of connections or message headers indirect information, such as a discrepancy between two internal operations that can be observed by an outsider Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include: the product's own users people or organizations whose information is created or used by the product, even if they are not direct product users the product's administrators, including the admins of the system(s) and/or networks on which the product operates the developer Information exposures can occur in different ways: the code explicitly inserts sensitive information into resources or messages that are intentionally made accessible to unauthorized actors, but should not contain the information - i.e., the information should have been "scrubbed" or "sanitized" a different weakness or mistake indirectly inserts the sensitive information into resources, such as a web script error revealing the full system path of the program. the code manages resources that intentionally contain sensitive information, but the resources are unintentionally made accessible to unauthorized actors. In this case, the information exposure is resultant - i.e., a different weakness enabled the access to the information in the first place. It is common practice to describe any loss of confidentiality as an "information exposure," but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or…
CWE-200 is a class-level weakness in MITRE’s Common Weakness Enumeration, with a MITRE likelihood of exploit of High. Applicable platforms: Language: Not Language-Specific; Technology: Not Technology-Specific; Technology: Web Based; Technology: Mobile.
Source: MITRE CWE (CWE-200 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.
Consequences
- Confidentiality — Read Application Data
Source: MITRE CWE, common consequences.
How CWE-200 is exploited in the wild
Threadlinqs maps 106 CVEs to CWE-200, published between 2017-02-13 and 2026-11-15. 4 are listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild, and 2 are tied to ransomware campaigns. By CVSS v3 severity the set splits into 6 critical, 29 high, 48 medium, 12 low. The highest EPSS score in the set is 99.9% (CVE-2024-24919), the modelled probability of exploitation in the next 30 days. 155 tracked threats reference CWE-200 directly or through a CVE it covers; the most recent is “WordPress 7.1.5 Security Release: 20 Core Fixes Including Template Part Block Permission Flaw (Potential RCE) and SQL Injection in WP_Meta_Query / Customizer Previews” (2026-11-19). Affected products concentrate in Google (11), Mozilla (9), Gitea (5), among 57 vendors in total.
Vulnerabilities (CVEs)
Showing 40 of 106 CVEs mapped to CWE-200, CISA KEV first, then by CVSS score.
- CVE-2024-24919 — CISA KEV · CVSS 8.6 high · EPSS 99.9% · published 2024-05-28
- CVE-2020-3259 — CISA KEV · CVSS 7.5 high · EPSS 71.7% · published 2020-05-06
- CVE-2026-20133 — CISA KEV · CVSS 6.5 medium · EPSS 31.8% · published 2026-02-25
- CVE-2025-68686 — CISA KEV · CVSS 5.3 medium · EPSS 0.4% · published 2026-02-10
- CVE-2026-87337 — CVSS 10 critical · EPSS 0.4% · published 2026-10-20
- CVE-2026-42164 — CVSS 9.8 critical · EPSS 0.1% · published 2026-08-17
- CVE-2026-55447 — CVSS 9.6 critical · EPSS 0.3% · published 2026-06-23
- CVE-2026-71424 — CVSS 9.6 critical · published 2026-08-17
- CVE-2026-82103 — CVSS 9.6 critical · published 2026-10-12
- CVE-2026-55450 — CVSS 9.3 critical · EPSS 0.3% · published 2026-06-23
- CVE-2026-80423 — CVSS 8.8 high · EPSS 0.3% · published 2026-09-23
- CVE-2026-83943 — CVSS 8.7 high · EPSS 0.3% · published 2026-10-08
- CVE-2026-107187 — CVSS 8.5 high · EPSS 0.2% · published 2026-10-19
- CVE-2026-21532 — CVSS 8.2 high · EPSS 0.8% · published 2026-02-05
- CVE-2026-78164 — CVSS 8.2 high · EPSS 0.3% · published 2026-10-19
- CVE-2024-3656 — CVSS 8.1 high · EPSS 2.8% · published 2024-10-09
- CVE-2026-93892 — CVSS 8.1 high · published 2026-10-12
- CVE-2026-60371 — CVSS 8 high · EPSS 0.2% · published 2026-07-22
- CVE-2026-93677 — CVSS 7.7 high · EPSS 0.4% · published 2026-10-07
- CVE-2026-85966 — CVSS 7.7 high · EPSS 0.2% · published 2026-10-12
- CVE-2026-4020 — CVSS 7.5 high · EPSS 2.2% · published 2026-03-31
- CVE-2026-30928 — CVSS 7.5 high · EPSS 1.6% · published 2026-03-10
- CVE-2026-32596 — CVSS 7.5 high · EPSS 1.5% · published 2026-03-18
- CVE-2023-25913 — CVSS 7.5 high · EPSS 0.6% · published 2023-08-21
- CVE-2026-85251 — CVSS 7.5 high · EPSS 0.5% · published 2026-10-19
- CVE-2025-6980 — CVSS 7.5 high · EPSS 0.4% · published 2025-10-23
- CVE-2026-60167 — CVSS 7.5 high · EPSS 0.3% · published 2026-07-21
- CVE-2026-21940 — CVSS 7.5 high · EPSS 0.3% · published 2026-01-20
- CVE-2026-47360 — CVSS 7.5 high · EPSS 0.3% · published 2026-10-01
- CVE-2026-55389 — CVSS 7.5 high · EPSS 0.3% · published 2026-07-28
- CVE-2026-73246 — CVSS 7.5 high · EPSS 0.3% · published 2026-08-11
- CVE-2026-67322 — CVSS 7.5 high · EPSS 0.3% · published 2026-08-01
- CVE-2026-72915 — CVSS 7.5 high · EPSS 0.2% · published 2026-08-10
- CVE-2026-16405 — CVSS 7.5 high · EPSS 0.2% · published 2026-07-21
- CVE-2026-67357 — CVSS 7.5 high · EPSS 0.2% · published 2026-08-02
- CVE-2026-55390 — CVSS 7.5 high · published 2026-07-28
- CVE-2026-92594 — CVSS 7.5 high · published 2026-09-16
- CVE-2024-38200 — CVSS 6.5 medium · EPSS 20.4% · published 2024-08-12
- CVE-2026-53959 — CVSS 6.5 medium · EPSS 1.0% · published 2026-08-18
- CVE-2026-66018 — CVSS 6.5 medium · EPSS 0.3% · published 2026-07-27
Affected vendors
Threat activity
155 tracked threats cite CWE-200; the 25 most recent are listed.
- WordPress 7.1.5 Security Release: 20 Core Fixes Including Template Part Block Permission Flaw (Potential RCE) and SQL Injection in WP_Meta_Query / Customizer PreviewsHIGH
- Microsoft agent-framework PyPI package compromised with .pth credential stealer (versions 1.26.1, 1.26.2)HIGH
- Mozilla Firefox 160 Security Update Fixes 99 Vulnerabilities Including 13 Sandbox Escape Flaws (MFSA 2026-125)HIGH
- Six Pre-Auth RCE Zero-Days (Stack Buffer Overflows) in Danfoss AK-SM800A Refrigeration Controllers (No CVEs Assigned)HIGH
- Ransomware Ecosystem Professionalization: Akira, Qilin, Play Business-Style Operations and Sicarii AI-Assembled Variant Lacking Working DecryptorMEDIUM
- Opportunistic Exploitation Attempts Against Copeland XWEB EVO Refrigeration Controller Flaws (CVE-2026-124014, CVE-2026-124010)CRITICAL
- Red Hat Satellite satellite/iop-vulnerability-engine-rhel9 container image - RHSA-2026:100152 (GitPython flaws CVE-2026-110856, CVE-2026-110858, CVE-2026-110859, CVE-2026-114145)CRITICAL
- Node.js November 2026 Security Releases Patch 16 Vulnerabilities (HTTP/2 crashes, HTTPS heap/TLS key leak CVE-2026-123864, TLS client-certificate auth bypass)HIGH
- Google Chrome 157 Stable Update Fixes 83 Security Flaws Including 5 Critical Use-After-Free Bugs (CVE-2026-126885, CVE-2026-126895, CVE-2026-126879, CVE-2026-126846, CVE-2026-126911)CRITICAL
- Malware and Credential Exposure in AI Agent Instruction Files (Skills, Hooks, MCP Configs) - Mitiga Skillgate ResearchHIGH
- Malicious npm package tw-pkgprobe-7731 targets developers integrating Twilio (credential harvesting)MEDIUM
- Operation Ghost Campus: AI Agents Steal OpenAI and DeepSeek API Keys From Exposed Servers and Harvest Data of 5,132 Chinese StudentsHIGH
- GhostAction Supply Chain Campaign Expands: Malicious GitHub Actions Workflow Steals Cloud and AI Credentials from Tens of Thousands of RepositoriesHIGH
- Able2Shell: 33 N-able N-central Vulnerabilities Chained into RCE and Root Privilege Escalation; N-able Takes Hosted Cloud OfflineCRITICAL
- AI Reward Hacking and Autonomous Sandbox Escape: OpenAI ExploitGym Evaluation Models Breach Hugging Face (Schneier DEF CON 34 Keynote Op-Ed)HIGH
- D-Link DGS-3130 Series Switches: Multiple Unpatched Zero-Days in D-Link Discovery Protocol (DDP) and Firmware (D-Link SAP10523, CVEs Pending)HIGH
- France Cyber Threat Outlook: Dark Web Credential Trade, Ransomware (Qilin/MedusaLocker/LockBit) and NoName057(16) HacktivismHIGH
- Multiple Vulnerabilities in Fortigate NGFW Before V7.4.1 on Siemens RUGGEDCOM APE1808 Devices (SSA-366067)CRITICAL
- OpenSSH on musl libc (Alpine Linux) authentication bypass via overly long password ("*sshole")CRITICAL
- Q3 2026 Ransomware Leak-Site Surge: 30% More Victims Driven by 43 New Groups, With Questionable ClaimsHIGH
- Increased Scanning for Vulnerable Legacy E-Mail Test Scripts (formail/mailtest.php variants, CVE-2000-0411 lineage)MEDIUM
- Threat Actor Impersonates ~32 AI Bots (ChatGPT, Claude, Perplexity, Meta) to Hunt for .env Secrets and API KeysMEDIUM
- Microsoft Edge Logic-Bug Full Exploit Chain Enables Code Execution Without Memory Corruption (Pwn2Own Berlin 2026, Orange Tsai; CVE-2026-45495)HIGH
- Compromised Injective SDK npm Package (@injectivelabs/sdk-ts 1.20.21) Exfiltrates Cryptocurrency Wallet KeysHIGH
- ProjectDiscovery Neo disclosure: 22 CVEs across 13 open-source projects (incl. Crawl4AI CVE-2026-26216 unauthenticated RCE, CVSS 9.8-10.0)CRITICAL
Mitigations
- Architecture and Design / Separation of Privilege: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Source: MITRE CWE, potential mitigations.
Detection methods (MITRE CWE)
- Automated Static Analysis - Binary or Bytecode (effectiveness: SOAR Partial): According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: Bytecode Weakness Analysis - including disassembler + source code weakness analysis Inter-application Flow Analysis
- Dynamic Analysis with Automated Results Interpretation (effectiveness: High): According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: Web Application Scanner Web Services Scanner Database Scanners
- Dynamic Analysis with Manual Results Interpretation (effectiveness: SOAR Partial): According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: Fuzz Tester Framework-based Fuzzer Automated Monitored Execution Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious
- Manual Static Analysis - Source Code (effectiveness: High): According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: Manual Source Code Review (not inspections)
- Automated Static Analysis - Source Code (effectiveness: High): According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: Context-configured Source Code Weakness Analyzer Cost effective for partial coverage: Source code Weakness Analyzer
- Architecture or Design Review (effectiveness: High): According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: Formal Methods / Correct-By-Construction Cost effective for partial coverage: Attack Modeling Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)
Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.