Threadlinqs IntelligenceStart free

Weakness · ClassCWE-345

CWE-345: Insufficient Verification of Data Authenticity

KEV-linkedClass

As of 2026-11-19, CWE-345 (Insufficient Verification of Data Authenticity) underlies 25 CVEs tracked by Threadlinqs, 1 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 62 tracked threats.

CVEs
25Mapped to CWE-345
CISA KEV
1Exploited in the wild
Critical
4CVSS v3 critical CVEs
Threats
62Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-345?

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

CWE-345 is a class-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Language: Not Language-Specific; Technology: ICS/OT.

Source: MITRE CWE (CWE-345 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.

Consequences

  • Integrity, Other — Varies by Context, Unexpected State

Source: MITRE CWE, common consequences.

How CWE-345 is exploited in the wild

Threadlinqs maps 25 CVEs to CWE-345, published between 2023-08-23 and 2026-11-16. 1 is listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild, and 1 is tied to ransomware campaigns. By CVSS v3 severity the set splits into 4 critical, 8 high, 10 medium, 1 low. The highest EPSS score in the set is 99.8% (CVE-2023-38831), the modelled probability of exploitation in the next 30 days. 62 tracked threats reference CWE-345 directly or through a CVE it covers; the most recent is “AI-Agent-Driven Intrusion Campaign Against Asian Government Systems (reported as Taiwan-targeted): Multi-Agent Password Spraying, SSO Pivoting and JWT 'none' Forgery” (2026-11-12). Affected products concentrate in CoreWCF (3), Microsoft (2), AMD (1), among 22 vendors in total.

Vulnerabilities (CVEs)

All 25 CVEs mapped to CWE-345, CISA KEV first, then by CVSS score.

Affected vendors

Threat activity

62 tracked threats cite CWE-345; the 25 most recent are listed.

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.