CWE · MITRE source
CWE-436Interpretation Conflict
Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.
This is generally found in proxies, firewalls, anti-virus software, and other intermediary devices that monitor, allow, deny, or modify traffic based on how the client or server is expected to behave.
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 3 framework(s): CAPEC 3 (partial) · ATT&CK 2 (partial) · OWASP-Web 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
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-2025-48384 KEV UPD | 10.0 | 8.0 | 0.0278 | 2025-07-08 |
CVE-2021-28474 | 8.0 | 8.8 | 0.5063 | 2021-05-11 |
CVE-2022-37436 | 8.0 | 5.3 | 0.5794 | 2023-01-17 |
CVE-2025-25292 | 8.0 | 9.8 | 0.6379 | 2025-03-12 |
CVE-2019-19589 | 7.0 | 9.8 | 0.0177 | 2019-12-05 |
CVE-2019-18792 | 7.0 | 9.1 | 0.0252 | 2020-01-06 |
CVE-2020-10180 | 7.0 | 9.8 | 0.0165 | 2020-03-05 |
CVE-2021-45327 | 7.0 | 9.8 | 0.0214 | 2022-02-08 |
CVE-2023-24813 | 7.0 | 10.0 | 0.0249 | 2023-02-07 |
CVE-2024-38428 | 7.0 | 9.1 | 0.0067 | 2024-06-16 |
CVE-2025-25291 | 7.0 | 9.8 | 0.1951 | 2025-03-12 |
CVE-2026-33807 | 7.0 | 9.1 | 0.0043 | 2026-04-15 |
CVE-2026-33808 | 7.0 | 9.1 | 0.0048 | 2026-04-15 |
CVE-2026-6270 | 7.0 | 9.1 | 0.0050 | 2026-04-16 |
CVE-2026-41248 | 7.0 | 9.1 | 0.0032 | 2026-04-24 |
CVE-2026-8034 UPD | 7.0 | 9.8 | 0.0038 | 2026-05-07 |
CVE-2026-14198 | 7.0 | 9.1 | 0.0030 | 2026-07-01 |
CVE-2018-6560 | 5.5 | 8.8 | 0.0042 | 2018-02-02 |
CVE-2018-19966 | 5.5 | 8.8 | 0.0044 | 2018-12-08 |
CVE-2019-0052 | 5.5 | 7.5 | 0.0184 | 2019-07-11 |
CVE-2019-17596 | 5.5 | 7.5 | 0.0469 | 2019-10-24 |
CVE-2020-9362 | 5.5 | 7.8 | 0.0149 | 2020-02-24 |
CVE-2020-9363 | 5.5 | 7.8 | 0.0095 | 2020-02-24 |
CVE-2020-10193 | 5.5 | 7.5 | 0.0135 | 2020-03-06 |
CVE-2020-3200 | 5.5 | 7.7 | 0.0172 | 2020-06-03 |