CWE · MITRE source
CWE-116Improper Encoding or Escaping of Output
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
Improper encoding or escaping can allow attackers to change the commands that are sent to another component, inserting malicious commands instead. Most products follow a certain protocol that uses structured messages for communication between components, such as queries or commands. These structured messages can contain raw data interspersed with metadata or control information. For example, "GET /index.html HTTP/1.1" is a structured message containing a command ("GET") with a single argument ("/index.html") and metadata about which protocol version is being used ("HTTP/1.1"). If an application uses attacker-supplied inputs to construct a structured message without properly encoding or escaping, then the attacker could insert special characters that will cause the data to be interpreted as control information or metadata. Consequently, the component that receives the output will perform the wrong operations, or otherwise interpret the data incorrectly.
Last updated: 11 August 2026 21:18 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 3 mapping(s) from 1 framework(s): CAPEC 3 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A05:2025 Injection.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
V1.1.2V1.2.1V1.2.3
NIST 800-53 r5 controls that address this weakness (1)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SI-15 | Information Output Filtering | SI | Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-36446 UPD | 9.9 | 9.8 | 0.9605 | 2022-07-25 |
CVE-2022-42948 KEV UPD | 9.9 | 9.8 | 0.0271 | 2023-03-24 |
CVE-2022-36099 UPD | 9.5 | 9.9 | 0.7589 | 2022-09-08 |
CVE-2022-36100 UPD | 9.5 | 9.9 | 0.7361 | 2022-09-08 |
CVE-2024-38475 KEV UPD | 9.5 | 9.1 | 0.9996 | 2024-07-01 |
CVE-2023-32071 UPD | 8.9 | 9.0 | 0.7114 | 2023-05-09 |
CVE-2017-8303 UPD | 8.7 | 9.8 | 0.2418 | 2017-05-05 |
CVE-2024-1874 UPD | 8.6 | 9.4 | 0.3257 | 2024-04-29 |
CVE-2026-20245 KEV UPD | 8.5 | 7.8 | 0.2532 | 2026-06-04 |
CVE-2022-30781 UPD | 8.4 | 7.5 | 0.8793 | 2022-05-16 |
CVE-2022-25235 UPD | 7.9 | 9.8 | 0.0495 | 2022-02-16 |
CVE-2022-29599 UPD | 7.9 | 9.8 | 0.0442 | 2022-05-23 |
CVE-2025-31651 UPD | 7.9 | 9.8 | 0.0405 | 2025-04-28 |
CVE-2019-10074 UPD | 7.8 | 9.8 | 0.0339 | 2019-09-11 |
CVE-2019-11325 UPD | 7.8 | 9.8 | 0.0335 | 2019-11-21 |
CVE-2021-28940 UPD | 7.8 | 9.8 | 0.0330 | 2021-04-02 |
CVE-2025-56266 | 7.8 | 9.8 | 0.0289 | 2025-09-08 |
CVE-2018-9246 UPD | 7.7 | 9.8 | 0.0258 | 2018-06-08 |
CVE-2018-15494 UPD | 7.7 | 9.8 | 0.0254 | 2018-08-18 |
CVE-2021-28662 UPD | 7.7 | 6.5 | 0.7187 | 2021-05-27 |
CVE-2021-31806 UPD | 7.7 | 6.5 | 0.9578 | 2021-05-27 |
CVE-2022-26174 UPD | 7.7 | 9.8 | 0.0242 | 2022-03-21 |
CVE-2024-38474 UPD | 7.7 | 9.8 | 0.0246 | 2024-07-01 |
CVE-2022-35153 UPD | 7.6 | 9.8 | 0.0170 | 2022-08-18 |
CVE-2021-42010 UPD | 7.6 | 9.8 | 0.0150 | 2022-10-24 |