Cyber Resilience

CWE · MITRE source

CWE-755Improper Handling of Exceptional Conditions

Abstraction: Class · CVEs in our corpus: 574

The product does not handle or incorrectly handles an exceptional condition.

Last updated: 04 July 2026 08:17 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: mostly · 3 mapping(s) from 2 framework(s): ATT&CK 2 (partial) · OWASP-Web 1 (mostly)

See the full cumulative-coverage rollup →

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 (10)AI

Control Title Family Why it addresses this CWE
CP-12Safe ModeCPSupplies a concrete handling action (safe mode) for exceptional conditions, mitigating risks from improper or absent handling that could allow continued attacks.
CP-3Contingency TrainingCPBy preparing users for contingency scenarios, the control promotes proper handling of exceptional conditions instead of default or unsafe behaviors.
CP-5Contingency Plan UpdateCPAn updated contingency plan defines current actions for exceptional conditions, reducing the window for attackers to exploit improper handling leading to system failure.
IR-1Policy and ProceduresIRProcedures ensure proper handling of exceptional conditions to support effective incident response.
IR-3Incident Response TestingIRIncident response testing confirms proper handling of exceptional conditions to limit exploit impact.
IR-7Incident Response AssistanceIRGives users guidance on incident handling, reducing improper handling of exceptional conditions that could stem from exploited weaknesses.
SI-13Predictable Failure PreventionSIPrepared component exchange provides a defined recovery path, making improper handling of failures less exploitable.
SI-17Fail-safe ProceduresSIMandates defined procedures that ensure exceptional conditions are handled in a controlled, secure manner instead of being ignored or mishandled.
AU-5Response to Audit Logging Process FailuresAUProvides defined handling (alert and additional actions) for the exceptional condition of audit logging failure.
SC-24Fail in Known StateSCEnforces structured response to exceptional conditions so the system cannot remain in an unsafe state.

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-2017-5638 KEV10.09.81.00002017-03-11
CVE-2018-0155 KEV10.08.60.07752018-03-28
CVE-2020-7247 KEV10.09.80.98952020-01-29
CVE-2021-38003 KEV10.08.80.36242021-11-23
CVE-2024-29748 KEV UPD10.07.80.00682024-04-05
CVE-2018-09348.07.50.66472018-03-14
CVE-2019-128158.09.80.57612019-07-19
CVE-2019-142878.08.80.63922019-10-17
CVE-2021-281658.07.50.53862021-04-01
CVE-2023-369338.07.50.72242023-07-05
CVE-2017-28777.09.80.01902018-09-19
CVE-2018-199917.09.80.02332018-12-10
CVE-2019-62567.09.80.02412019-01-14
CVE-2019-144317.09.80.03632019-07-29
CVE-2019-171957.09.80.11032019-10-15
CVE-2009-50437.09.80.01232019-10-31
CVE-2020-110127.09.30.02102020-04-23
CVE-2020-247537.09.80.02642020-09-17
CVE-2020-138597.09.80.01182021-02-01
CVE-2021-361287.09.80.01502021-07-02
CVE-2021-383847.09.80.01462021-08-10
CVE-2021-432727.09.80.03522021-11-14
CVE-2021-403917.09.80.02922021-11-19
CVE-2021-238597.09.10.00972021-12-08
CVE-2022-317997.09.80.01872022-06-02