What is CWE-20?
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Input validation is a frequently-used technique for checking potentially dangerous inputs in order to ensure that the inputs are safe for processing within the code, or when communicating with other components. Input can consist of: raw data - strings, numbers, parameters, file contents, etc. metadata - information about the raw data, such as headers or size Data can be simple or structured. Structured data can be composed of many nested layers, composed of combinations of metadata and raw data, with other simple or structured data. Many properties of raw data or metadata may need to be validated upon entry into the code, such as: specified quantities such as size, length, frequency, price, rate, number of operations, time, etc. implied or derived quantities, such as the actual size of a file instead of a specified size indexes, offsets, or positions into more complex data structures symbolic keys or other elements into hash tables, associative arrays, etc. well-formedness, i.e. syntactic correctness - compliance with expected syntax lexical token correctness - compliance with rules for what is treated as a token specified or derived type - the actual type of the input (or what the input appears to be) consistency - between individual data elements, between raw data and metadata, between references, etc. conformance to domain-specific rules, e.g. business logic equivalence - ensuring that equivalent inputs are treated the same authenticity, ownership, or other attestations about the input, e.g. a cryptographic signature to prove the source of the data Implied or derived properties of data must often be calculated or inferred by the code itself. Errors in deriving properties may be considered a contributing factor to improper input validation.
CWE-20 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.
Source: MITRE CWE (CWE-20 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.
Consequences
- Availability — DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory). An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
- Confidentiality — Read Memory, Read Files or Directories. An attacker could read confidential data if they are able to control resource references.
- Integrity, Confidentiality, Availability — Modify Memory, Execute Unauthorized Code or Commands. An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Source: MITRE CWE, common consequences.
How CWE-20 is exploited in the wild
Threadlinqs maps 156 CVEs to CWE-20, published between 2010-05-07 and 2026-11-12. 19 are listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild, and 6 are tied to ransomware campaigns. By CVSS v3 severity the set splits into 52 critical, 56 high, 37 medium, 2 low. The highest EPSS score in the set is 99.9% (CVE-2024-3400), the modelled probability of exploitation in the next 30 days. 234 tracked threats reference CWE-20 directly or through a CVE it covers; the most recent is “DragonForce Ransomware Cartel Windows Payload Analysis (.df_win, ChaCha20/RSA-4096, ARP/SMB Discovery)” (2026-11-17). Affected products concentrate in Google (38), Microsoft (15), Adobe (9), among 63 vendors in total.
Vulnerabilities (CVEs)
Showing 40 of 156 CVEs mapped to CWE-20, CISA KEV first, then by CVSS score.
- CVE-2021-44228 — CISA KEV · CVSS 10 critical · EPSS 99.9% · published 2021-12-10
- CVE-2024-3400 — CISA KEV · CVSS 10 critical · EPSS 99.9% · published 2024-04-12
- CVE-2023-22515 — CISA KEV · CVSS 10 critical · EPSS 99.2% · published 2023-10-04
- CVE-2026-34910 — CISA KEV · CVSS 10 critical · EPSS 45.7% · published 2026-05-22
- CVE-2025-20393 — CISA KEV · CVSS 10 critical · EPSS 32.3% · published 2025-12-17
- CVE-2026-93952 — CISA KEV · CVSS 10 critical · EPSS 1.0% · published 2026-09-22
- CVE-2018-7600 — CISA KEV · CVSS 9.8 critical · EPSS 99.9% · published 2018-03-29
- CVE-2023-23397 — CISA KEV · CVSS 9.8 critical · EPSS 97.1% · published 2023-03-14
- CVE-2024-21413 — CISA KEV · CVSS 9.8 critical · EPSS 94.6% · published 2024-02-13
- CVE-2026-12569 — CISA KEV · CVSS 9.8 critical · EPSS 1.1% · published 2026-06-18
- CVE-2023-2868 — CISA KEV · CVSS 9.4 critical · EPSS 86.8% · published 2023-05-24
- CVE-2025-54236 — CISA KEV · CVSS 9.1 critical · EPSS 95.3% · published 2025-09-09
- CVE-2026-34197 — CISA KEV · CVSS 8.8 high · EPSS 15.4% · published 2026-04-01
- CVE-2015-2291 — CISA KEV · CVSS 7.8 high · EPSS 9.0% · published 2017-08-09
- CVE-2023-41061 — CISA KEV · CVSS 7.8 high · EPSS 4.3% · published 2023-09-07
- CVE-2018-0171 — CISA KEV · CVSS 7.5 high · EPSS 99.5% · published 2018-03-28
- CVE-2026-6973 — CISA KEV · CVSS 7.2 high · EPSS 2.5% · published 2026-05-07
- CVE-2021-38000 — CISA KEV · CVSS 6.1 medium · EPSS 4.9% · published 2021-11-23
- CVE-2025-8876 — CISA KEV · EPSS 3.4% · published 2025-08-14
- CVE-2026-21858 — CVSS 10 critical · EPSS 78.1% · published 2026-01-08
- CVE-2026-48316 — CVSS 10 critical · EPSS 1.1% · published 2026-07-06
- CVE-2026-48277 — CVSS 10 critical · EPSS 0.8% · published 2026-06-30
- CVE-2026-48281 — CVSS 10 critical · EPSS 0.8% · published 2026-06-30
- CVE-2026-54402 — CVSS 9.9 critical · EPSS 1.7% · published 2026-07-02
- CVE-2026-50748 — CVSS 9.9 critical · EPSS 1.6% · published 2026-07-02
- CVE-2026-28336 — CVSS 9.9 critical · EPSS 1.6% · published 2026-11-03
- CVE-2026-20303 — CVSS 9.9 critical · EPSS 0.4% · published 2026-08-05
- CVE-2017-12611 — CVSS 9.8 critical · EPSS 87.1% · published 2017-09-20
- CVE-2016-7407 — CVSS 9.8 critical · EPSS 5.5% · published 2017-03-03
- CVE-2026-41293 — CVSS 9.8 critical · EPSS 1.6% · published 2026-05-12
- CVE-2026-69845 — CVSS 9.8 critical · EPSS 1.0% · published 2026-09-08
- CVE-2026-20093 — CVSS 9.8 critical · EPSS 0.9% · published 2026-04-01
- CVE-2026-65637 — CVSS 9.8 critical · EPSS 0.5% · published 2026-08-25
- CVE-2026-84325 — CVSS 9.8 critical · EPSS 0.4% · published 2026-09-01
- CVE-2026-7808 — CVSS 9.8 critical · EPSS 0.3% · published 2026-08-23
- CVE-2026-53412 — CVSS 9.8 critical · published 2026-07-16
- CVE-2022-39266 — CVSS 9.7 critical · EPSS 1.2% · published 2022-09-29
- CVE-2024-23469 — CVSS 9.6 critical · EPSS 17.8% · published 2024-07-17
- CVE-2026-17655 — CVSS 9.6 critical · EPSS 0.5% · published 2026-07-30
- CVE-2026-48284 — CVSS 9.6 critical · EPSS 0.4% · published 2026-07-14
Affected vendors
- Google — 38 CVEs
- Microsoft — 15 CVEs
- Adobe — 9 CVEs
- Cisco — 8 CVEs
- Apache Software Foundation — 6 CVEs
- Ubiquiti Inc — 4 CVEs
- Zoom Communications — 4 CVEs
- Ivanti — 3 CVEs
- PTC — 3 CVEs
- Splunk — 3 CVEs
- vllm-project — 3 CVEs
- Apache — 2 CVEs
Threat activity
234 tracked threats cite CWE-20; the 25 most recent are listed.
- DragonForce Ransomware Cartel Windows Payload Analysis (.df_win, ChaCha20/RSA-4096, ARP/SMB Discovery)HIGH
- Mozilla Firefox 160 Security Update Fixes 99 Vulnerabilities Including 13 Sandbox Escape Flaws (MFSA 2026-125)HIGH
- Dragos Q3 2026: Industrial Ransomware Incidents Up 11% to 1,266, Manufacturing 69% of VictimsHIGH
- Cron-Based Persistence on Network Appliances: Evooo1Bot and SSHStalker Linux BotnetsHIGH
- PTC Windchill and FlexPLM Critical RCE via Deserialization of Untrusted Data (CVE-2026-126325)CRITICAL
- Ivanti EPM Core Critical SQL Injection Enabling Unauthenticated RCE (CVE-2026-121653) and Multiple Ivanti CSA/EPMM/Sentry/UWM FlawsCRITICAL
- PostgreSQL CVE-2026-6460: 22-Year-Old Composite Type Confusion Enables Authenticated RCE; 52 CVEs Fixed in 18.7/17.12/16.16/15.20/14.25HIGH
- ARTEX open-source agentic AI pentest framework abused by Chinese-nexus state and criminal actors to automate intrusions at machine speed (FBI Flash Alert)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
- Intel and AMD November 2026 Patch Tuesday: 200+ vulnerabilities incl. critical TDX MigTD flaws (CVE-2026-61887, CVE-2026-44685, CVE-2026-61473)CRITICAL
- Critical Zoom Workplace for Windows Flaws (CVE-2026-108186, CVE-2026-108187) Allow Unauthenticated Remote Privilege EscalationCRITICAL
- CVE-2026-119618: Critical Unauthenticated RCE via Race Condition in Apache HTTP Server mod_http2 assign_headers()CRITICAL
- Zoom Workplace for Windows Critical Privilege Escalation (CVE-2026-108186, CVE-2026-108187) and ASUS Router Firmware Remote File Access Vulnerabilities (CVE-2026-88707 to CVE-2026-88710) PatchedCRITICAL
- CTO at NCSC Weekly Summary (week ending July 26, 2026): Cl0p PTC Windchill/FlexPLM exploitation (CVE-2026-12569), SonicWall SMA 1000 zero-days (CVE-2026-15409/CVE-2026-15410), and multi-actor state-linked activityHIGH
- Xen Orchestra Authentication Bypass (VSA-2026-062) Actively Exploited to Hijack VM ServersCRITICAL
- Multiple Vulnerabilities in Google Chrome prior to 156.0.8078.73 (52 CVEs incl. CVE-2026-118306 FileSystem sandbox escape) - HKCERT Alert A26-10-59CRITICAL
- BO Team (Black Owl) Supply Chain Attack Against a Software Developer's Infrastructure (CVE-2021-44228)HIGH
- Siemens SSA-364175: Multiple Vulnerabilities in Palo Alto Networks Virtual NGFW on RUGGEDCOM APE1808 (CVE-2024-3596, CVE-2025-4231 and others)CRITICAL
- Software Supply Chain Attacks Overview: CCleaner, Codecov, SolarWinds Orion, npm Shai-Hulud, Kaseya VSA, MOVEit TransferHIGH
- Apple September 2026 Security Updates: 273 CVEs incl. actively exploited Screen Sharing auth bypass (CVE-2026-65400) and critical Bluetooth RCE (CVE-2026-65414)CRITICAL
- Multiple Vulnerabilities in Microsoft Edge (prior to 157.0.4341.42) - 27 Chromium CVEs - HK GovCERT A26-11-10HIGH
- Metasploit 6.5.9 Wrapup: Public Exploit Modules for Citrix NetScaler (CVE-2026-88771), Cisco Secure Email Gateway (CVE-2026-76461/76443), GitLab CI/CD Regex RCE (CVE-2026-97229), OpenBullet2, Flowise, SPIP and WordPress Bug LibraryCRITICAL
- Multiple Vulnerabilities in Google Chrome (prior to 156.0.8078.79) - CVE-2026-76024 to CVE-2026-76031, CVE-2026-119260 to CVE-2026-119272HIGH
- GhostMap: Android ZIP-parsing flaw (libziparchive/libandroidfw mismatch) lets a malicious APK trigger a persistent system_server crash loopMEDIUM
- Fastjson 1.x Gadget-Free RCE (CVE-2026-16723 / ThreatBook XVE-2026-39684) Under Active ExploitationCRITICAL
Mitigations
- Architecture and Design / Attack Surface Reduction: Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build "recognizers" for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses. [REF-1109] [REF-1110] [REF-1111]
- Architecture and Design / Libraries or Frameworks: Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Architecture and Design, Implementation / Attack Surface Reduction: Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
- Implementation / Input Validation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected…
- Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server. Even though client-side checks provide minimal benefits with respect to server-side security, they are still useful. First, they can support intrusion detection. If the server receives input that should have been rejected by the client, then it may be an indication of an attack. Second, client-side error-checking…
- Implementation: When your application combines data from multiple sources, perform the validation after the sources have been combined. The individual data elements may pass the validation step but violate the intended restrictions after they have been combined.
- Implementation: Be especially careful to validate all input when invoking code that crosses language boundaries, such as from an interpreted language to native code. This could create an unexpected interaction between the language boundaries. Ensure that you are not violating any of the expectations of the language with which you are interfacing. For example, even though Java may not be susceptible to buffer overflows, providing a large argument in a call to native code might trigger an overflow.
- Implementation: Directly convert your input type into the expected data type, such as using a conversion function that translates a string into a number. After converting to the expected data type, ensure that the input's values fall within the expected range of allowable values and that multi-field consistencies are maintained.
- Implementation: Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174). Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked. Use libraries such as the OWASP ESAPI Canonicalization control. Consider performing repeated canonicalization until your input does not change any more. This will avoid double-decoding and similar scenarios, but it might inadvertently modify inputs that are allowed to contain properly-encoded dangerous content.
- Implementation: When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.
Source: MITRE CWE, potential mitigations.
Detection methods (MITRE CWE)
- Automated Static Analysis: Some instances of improper input validation can be detected using automated static analysis. A static analysis tool might allow the user to specify which application-specific methods or functions perform input validation; the tool might also have built-in knowledge of validation frameworks such as Struts. The tool may then suppress or de-prioritize any associated warnings. This allows the analyst to focus on areas of the software in which input validation does not appear to be present. Except…
- Manual Static Analysis: When custom input validation is required, such as when enforcing business rules, manual analysis is necessary to ensure that the validation is properly implemented.
- Fuzzing: Fuzzing techniques can be useful for detecting input validation errors. When unexpected inputs are provided to the software, the software should not crash or otherwise become unstable, and it should generate application-controlled error messages. If exceptions or interpreter-generated error messages occur, this indicates that the input was not detected and handled within the application logic itself.
- 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 Binary Weakness Analysis - including disassembler + source code weakness analysis
- Manual 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: Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies
- 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: High): According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: Fuzz Tester Framework-based Fuzzer Cost effective for partial coverage: Host Application Interface Scanner 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: Focused Manual Spotcheck - Focused manual analysis of source Manual Source Code Review (not inspections)
Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.