What is CWE-778?
When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.
When security-critical events are not logged properly, such as a failed login attempt, this can make malicious behavior more difficult to detect and may hinder forensic analysis after an attack succeeds. As organizations adopt cloud storage resources, these technologies often require configuration changes to enable detailed logging information, since detailed logging can incur additional costs. This could lead to telemetry gaps in critical audit logs. For example, in Azure, the default value for logging is disabled.
CWE-778 is a base-level weakness in MITRE’s Common Weakness Enumeration, with a MITRE likelihood of exploit of Medium. Applicable platforms: Language: Not Language-Specific; Technology: Cloud Computing; Technology: Not Technology-Specific.
Source: MITRE CWE (CWE-778 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.
Consequences
- Non-Repudiation — Hide Activities. If security critical information is not recorded, there will be no trail for forensic analysis and discovering the cause of problems or the source of attacks may become more difficult or impossible.
Source: MITRE CWE, common consequences.
How CWE-778 is exploited in the wild
Threadlinqs maps 3 CVEs to CWE-778, published between 2026-07-30 and 2026-10-12. None of them is in the CISA KEV catalog yet. By CVSS v3 severity the set splits into 1 high, 1 medium, 1 low. The highest EPSS score in the set is 0.3% (CVE-2026-85959), the modelled probability of exploitation in the next 30 days. 10 tracked threats reference CWE-778 directly or through a CVE it covers; the most recent is “China-nexus WARP PANDA exploits VMware ESXi insufficient-logging flaw (CVE-2026-41709) against law firms” (2026-10-29). Affected products concentrate in IBM (1), Progress Software Corporation (1), VMware (1).
Vulnerabilities (CVEs)
All 3 CVEs mapped to CWE-778, CISA KEV first, then by CVSS score.
- CVE-2026-85959 — CVSS 7.5 high · EPSS 0.3% · published 2026-10-12
- CVE-2026-18161 — CVSS 4.3 medium · EPSS 0.2% · published 2026-09-22
- CVE-2026-41709 — CVSS 2.7 low · EPSS 0.2% · published 2026-07-30
Affected vendors
Threat activity
10 tracked threats cite CWE-778:
- China-nexus WARP PANDA exploits VMware ESXi insufficient-logging flaw (CVE-2026-41709) against law firmsHIGH
- Warp Panda exploits VMware ESX CVE-2026-41709; PHP2Shell (CVE-2026-109618/109619) chained with Fragnesia (CVE-2026-46300) to root firewallsCRITICAL
- CISA adds two KEVs: Broadcom VMware ESX CVE-2026-41709 (Insufficient Logging) and Linux Kernel CVE-2026-46300 (Fragnesia ESP-in-TCP page-cache LPE)CRITICAL
- Progress MarkLogic Server: 31 Vulnerabilities (CVE-2026-9191, CVE-2026-85947 through CVE-2026-85976) Enabling Privilege Escalation, Code Execution and Authentication BypassCRITICAL
- Three Critical VMware Flaws (CVE-2026-59309, CVE-2026-59310, CVE-2026-47876) Allow Auth Bypass, RCE, and VM EscapeCRITICAL
- OAuth Client ID Spoofing Enables Stealthy Enumeration and Credential Validation Against Microsoft Entra ID (UNK_pyreq2323 / UNK_OutFlareAZ)HIGH
- XMRig CoinMiner and ShellBot (PerlBot) Campaign Targeting Linux SSH Servers via SSH Brute-ForceHIGH
- GigaWiper: Multi-Stage Destructive Windows Backdoor Combining Disk Wiping, File Encryption, and Boot Sabotage (CyberAv3ngers/Crucio/FlockWiper Lineage)HIGH
- Compromised RD Session Host Used to Stage Boots-Themed Phishing Campaign via Gammadyne MailerMEDIUM
- Lazarus Group Medusa Ransomware — North Korean State-Backed Extortion Targeting US Healthcare and Middle EastCRITICAL
Mitigations
- Architecture and Design: Use a centralized logging mechanism that supports multiple levels of detail.
- Implementation: Ensure that all security-related successes and failures can be logged. When storing data in the cloud (e.g., AWS S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to enable and capture detailed logging information.
- Operation: Be sure to set the level of logging appropriately in a production environment. Sufficient data should be logged to enable system administrators to detect attacks, diagnose errors, and recover from attacks. At the same time, logging too much data (CWE-779) can cause the same problems, including unexpected costs when using a cloud environment.
- Operation: To enable storage logging using Azure's Portal, navigate to the name of the Storage Account, locate Monitoring (CLASSIC) section, and select Diagnostic settings (classic). For each of the various properties (blob, file, table, queue), ensure the status is properly set for the desired logging data. If using PowerShell, the Set-AzStorageServiceLoggingProperty command could be called using appropriate -ServiceType, -LoggingOperations, and -RetentionDays arguments.
Source: MITRE CWE, potential mitigations.
Detection methods (MITRE CWE)
- Automated Static Analysis (effectiveness: High): Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.