CWE · MITRE source
CWE-158Improper Neutralization of Null Byte or NUL Character
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.
As data is parsed, an injected NUL character or null byte may cause the product to believe the input is terminated earlier than it actually is, or otherwise cause the input to be misinterpreted. This could then be used to inject potentially dangerous input that occurs after the null byte or otherwise bypass validation routines and other protection mechanisms.
Last updated: 19 November 2026 21:43 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: full · 17 mapping(s) from 4 framework(s): ATT&CK 10 (full) · ISO_IEC_27002_2022 5 (mostly) · 1 (mostly) · 800-53 1 (mostly)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
V1.2.10
NIST 800-53 r5 controls PROPOSED for this weakness (0)
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-47812 KEV UPD | 10.0 | 10.0 | 0.9388 | 2025-07-10 |
CVE-2009-1537 KEV UPD | 9.2 | 8.8 | 0.5108 | 2009-05-29 |
CVE-2020-14500 UPD | 7.7 | 10.0 | 0.0167 | 2020-08-25 |
CVE-2025-14388 UPD | 7.3 | 9.8 | 0.0048 | 2025-12-23 |
CVE-2022-20812 UPD | 6.7 | 9.0 | 0.0198 | 2022-07-06 |
CVE-2022-20813 UPD | 6.6 | 9.0 | 0.0114 | 2022-07-06 |
CVE-2023-5719 UPD | 6.6 | 8.8 | 0.0062 | 2023-11-06 |
CVE-2025-55113 UPD | 6.2 | 9.0 | 0.0029 | 2025-09-16 |
CVE-2026-33191 | 6.2 | 8.6 | 0.0040 | 2026-03-20 |
CVE-2026-76354 | 6.1 | 8.1 | 0.0044 | 2026-08-19 |
CVE-2020-5363 UPD | 6.0 | 8.6 | 0.0032 | 2020-06-10 |
CVE-2025-66263 UPD | 5.8 | 7.5 | 0.0042 | 2025-11-26 |
CVE-2025-1936 UPD | 5.7 | 7.3 | 0.0044 | 2025-03-04 |
CVE-2026-92705 | 5.6 | 7.8 | 0.0013 | 2026-10-09 |
CVE-2020-7928 UPD | 5.4 | 6.5 | 0.0144 | 2020-11-23 |
CVE-2024-10921 UPD | 5.3 | 6.8 | 0.0055 | 2024-11-14 |
CVE-2026-23863 UPD | 5.1 | 6.5 | 0.0053 | 2026-05-01 |
CVE-2026-115473 UPD | 5.0 | 6.5 | 0.0026 | 2026-11-04 |
CVE-2026-105239 | 4.6 | 5.3 | 0.0082 | 2026-10-06 |
CVE-2026-105240 | 4.6 | 5.3 | 0.0081 | 2026-10-06 |
CVE-2026-70603 UPD | 4.4 | 6.0 | 0.0013 | 2026-08-05 |
CVE-2026-129512 | 4.4 | 5.3 | 0.0037 | 2026-11-17 |
CVE-2024-0408 UPD | 4.3 | 5.5 | 0.0032 | 2024-01-18 |
CVE-2026-41256 UPD | 4.2 | 5.5 | 0.0016 | 2026-05-11 |
CVE-2026-118767 | 3.8 | 4.8 | 0.0022 | 2026-10-29 |