CWE · MITRE source
CWE-758Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
The product uses an API function, data structure, or other entity in a way that relies on properties that are not always guaranteed to hold for that entity.
This can lead to resultant weaknesses when the required properties change, such as when the product is ported to a different platform or if an interaction error (CWE-435) occurs.
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: partial · 6 mapping(s) from 1 framework(s): ATT&CK 6 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| 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). 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-2026-22858 UPD | 7.0 | 9.1 | 0.0060 | 2026-01-14 |
CVE-2026-4705 | 7.0 | 9.8 | 0.0042 | 2026-03-24 |
CVE-2026-4724 | 7.0 | 9.1 | 0.0032 | 2026-03-24 |
CVE-2025-54811 | 5.5 | 7.1 | 0.0020 | 2025-10-01 |
CVE-2026-21677 | 5.5 | 8.8 | 0.0031 | 2026-01-06 |
CVE-2026-21684 | 5.5 | 7.1 | 0.0024 | 2026-01-07 |
CVE-2026-21685 | 5.5 | 7.1 | 0.0024 | 2026-01-07 |
CVE-2026-21686 | 5.5 | 7.1 | 0.0024 | 2026-01-07 |
CVE-2026-21687 | 5.5 | 7.1 | 0.0024 | 2026-01-07 |
CVE-2026-24404 | 5.5 | 7.1 | 0.0040 | 2026-01-24 |
CVE-2026-24407 | 5.5 | 7.1 | 0.0040 | 2026-01-24 |
CVE-2026-24409 | 5.5 | 7.1 | 0.0031 | 2026-01-24 |
CVE-2026-24410 | 5.5 | 7.1 | 0.0031 | 2026-01-24 |
CVE-2026-24411 | 5.5 | 7.1 | 0.0031 | 2026-01-24 |
CVE-2026-4718 | 5.5 | 8.1 | 0.0030 | 2026-03-24 |
CVE-2024-4774 | 3.5 | 6.5 | 0.0037 | 2024-05-14 |
CVE-2025-55160 UPD | 3.5 | 6.1 | 0.0038 | 2025-08-13 |
CVE-2026-28528 | 3.5 | 4.6 | 0.0014 | 2026-03-30 |
CVE-2026-34533 | 3.5 | 6.2 | 0.0016 | 2026-03-31 |
CVE-2026-34537 | 3.5 | 6.2 | 0.0016 | 2026-03-31 |
CVE-2026-34547 | 3.5 | 6.2 | 0.0016 | 2026-03-31 |
CVE-2026-34549 | 3.5 | 6.2 | 0.0016 | 2026-03-31 |
CVE-2023-30624 | 1.6 | 3.9 | 0.0045 | 2023-04-27 |
CVE-2026-40279 | 1.5 | 3.7 | 0.0024 | 2026-04-21 |
CVE-2024-58350 | 1.5 | 2.9 | 0.0011 | 2026-06-10 |