CWE · MITRE source
CWE-197Numeric Truncation Error
Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.
When a primitive is cast to a smaller primitive, the high order bits of the large value are lost in the conversion, potentially resulting in an unexpected value that is not equal to the original value. This value may be required as an index into a buffer, a loop iterator, or simply necessary state data. In any case, the value cannot be trusted and the system will be in an undefined state. While this method may be employed viably to isolate the low bits of a value, this usage is rare, and truncation usually implies that an implementation error has occurred.
Last updated: 16 October 2026 14:24 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
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. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-42475 KEV UPD | 9.9 | 9.8 | 0.9947 | 2023-01-02 |
CVE-2024-43639 | 8.1 | 9.8 | 0.0894 | 2024-11-12 |
CVE-2025-6965 UPD | 8.1 | 7.7 | 0.7330 | 2025-07-15 |
CVE-2026-96113 | 7.4 | 9.8 | 0.0067 | 2026-10-13 |
CVE-2024-28944 UPD | 7.0 | 8.8 | 0.0235 | 2024-04-09 |
CVE-2024-21352 UPD | 6.9 | 8.8 | 0.0163 | 2024-02-13 |
CVE-2024-21391 UPD | 6.9 | 8.8 | 0.0163 | 2024-02-13 |
CVE-2024-21440 UPD | 6.9 | 8.8 | 0.0203 | 2024-03-12 |
CVE-2024-21451 UPD | 6.9 | 8.8 | 0.0195 | 2024-03-12 |
CVE-2024-30009 UPD | 6.9 | 8.8 | 0.0171 | 2024-05-14 |
CVE-2024-49018 | 6.9 | 8.8 | 0.0154 | 2024-11-12 |
CVE-2024-21310 UPD | 6.8 | 7.8 | 0.1151 | 2024-01-09 |
CVE-2023-32143 UPD | 6.8 | 8.8 | 0.0113 | 2024-05-03 |
CVE-2024-43519 UPD | 6.8 | 8.8 | 0.0150 | 2024-10-08 |
CVE-2026-87529 | 6.8 | 9.6 | 0.0050 | 2026-09-09 |
CVE-2026-78512 UPD | 6.7 | 8.8 | 0.0082 | 2026-09-08 |
CVE-2026-102225 | 6.7 | 8.8 | 0.0080 | 2026-10-13 |
CVE-2020-15202 UPD | 6.6 | 9.0 | 0.0129 | 2020-09-25 |
CVE-2024-29050 UPD | 6.6 | 8.4 | 0.0125 | 2024-04-09 |
CVE-2024-38125 | 6.6 | 7.8 | 0.0594 | 2024-08-13 |
CVE-2026-108450 | 6.5 | 8.8 | 0.0044 | 2026-10-15 |
CVE-2026-108451 | 6.5 | 8.8 | 0.0044 | 2026-10-15 |
CVE-2026-68880 UPD | 6.2 | 8.0 | 0.0077 | 2026-09-08 |
CVE-2026-69512 UPD | 6.1 | 8.0 | 0.0056 | 2026-09-08 |
CVE-2023-36710 UPD | 6.0 | 7.8 | 0.0093 | 2023-10-10 |