CWE · MITRE source
CWE-248Uncaught Exception
An exception is thrown from a function, but it is not caught.
When an exception is not caught, it may cause the program to crash or expose sensitive information.
Last updated: 04 July 2026 00:28 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 · 3 mapping(s) from 2 framework(s): ATT&CK 2 (mostly) · OWASP-Web 1 (full)
OWASP Top 10 for Web (2025)
This weakness contributes to A10:2025 Mishandling of Exceptional Conditions.
NIST 800-53 r5 controls that address this weakness (2)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-24 | Fail in Known State | SC | Prevents abrupt termination from uncaught exceptions by requiring a defined, preserved-state failure mode. |
SI-17 | Fail-safe Procedures | SI | Requires pre-defined safe responses for uncaught exceptions so they do not result in undefined or insecure program termination. |
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). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2018-11466 | 7.0 | 9.8 | 0.0397 | 2018-12-12 |
CVE-2024-42037 | 7.0 | 9.3 | 0.0012 | 2024-08-08 |
CVE-2025-67647 | 7.0 | 9.1 | 0.0047 | 2026-01-15 |
CVE-2016-10363 | 5.5 | 7.5 | 0.0132 | 2017-06-16 |
CVE-2018-11465 | 5.5 | 7.8 | 0.0043 | 2018-12-12 |
CVE-2019-6575 UPD | 5.5 | 7.5 | 0.0163 | 2019-04-17 |
CVE-2018-7852 | 5.5 | 7.5 | 0.0361 | 2019-05-22 |
CVE-2019-10931 | 5.5 | 7.5 | 0.0152 | 2019-07-11 |
CVE-2019-6809 | 5.5 | 7.5 | 0.0176 | 2019-09-17 |
CVE-2019-6828 | 5.5 | 7.5 | 0.0153 | 2019-09-17 |
CVE-2019-6829 | 5.5 | 7.5 | 0.0161 | 2019-09-17 |
CVE-2020-5129 | 5.5 | 7.5 | 0.0130 | 2020-03-26 |
CVE-2020-10604 | 5.5 | 7.5 | 0.0215 | 2020-07-25 |
CVE-2020-10292 | 5.5 | 8.2 | 0.0145 | 2020-11-06 |
CVE-2020-6019 | 5.5 | 7.5 | 0.0279 | 2020-11-13 |
CVE-2020-15796 | 5.5 | 7.5 | 0.0159 | 2020-12-14 |
CVE-2021-37714 | 5.5 | 7.5 | 0.0687 | 2021-08-18 |
CVE-2021-33010 | 5.5 | 7.5 | 0.0103 | 2022-04-04 |
CVE-2022-24822 | 5.5 | 7.5 | 0.0159 | 2022-04-06 |
CVE-2022-20761 | 5.5 | 7.4 | 0.0035 | 2022-04-15 |
CVE-2021-41545 | 5.5 | 7.5 | 0.0085 | 2022-05-10 |
CVE-2022-20919 | 5.5 | 8.6 | 0.0101 | 2022-09-30 |
CVE-2022-39386 | 5.5 | 7.5 | 0.0073 | 2022-11-08 |
CVE-2022-41940 | 5.5 | 7.1 | 0.0194 | 2022-11-22 |
CVE-2022-38166 | 5.5 | 7.5 | 0.0065 | 2022-11-25 |