CWE · MITRE source
CWE-940Improper Verification of Source of a Communication Channel
The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
When an attacker can successfully establish a communication channel from an untrusted origin, the attacker may be able to gain privileges and access unexpected functionality.
Last updated: 20 August 2026 20:22 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 · 4 mapping(s) from 1 framework(s): CAPEC 4 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
V3.5.3V10.6.2V15.2.4
NIST 800-53 r5 controls that address this weakness (4)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-11 | Trusted Path | SC | Requires explicit verification of the source and integrity of the channel used for authentication and other security functions. |
SC-20 | Secure Name/Address Resolution Service (Authoritative Source) | SC | Provides the means to verify the source of name-resolution responses instead of relying on unauthenticated channels. |
SC-23 | Session Authenticity | SC | Requires explicit verification of the communication source, blocking session hijacking via spoofed or alternate channels. |
IA-9 | Service Identification and Authentication | IA | Enforces verification of the source of a communication channel by requiring identification and authentication of services first. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-61932 KEV | 9.9 | 9.8 | 0.0263 | 2025-10-20 |
CVE-2023-41094 UPD | 7.4 | 10.0 | 0.0057 | 2023-10-04 |
CVE-2023-41355 UPD | 7.4 | 9.8 | 0.0062 | 2023-11-03 |
CVE-2024-40515 UPD | 7.4 | 9.8 | 0.0066 | 2024-07-16 |
CVE-2024-38886 UPD | 7.4 | 9.8 | 0.0064 | 2024-08-02 |
CVE-2023-48387 UPD | 6.8 | 8.8 | 0.0103 | 2023-12-15 |
CVE-2023-3663 UPD | 6.7 | 8.8 | 0.0102 | 2023-08-03 |
CVE-2026-2611 UPD | 6.7 | 9.6 | 0.0038 | 2026-05-19 |
CVE-2025-59159 UPD | 6.6 | 9.6 | 0.0024 | 2025-10-06 |
CVE-2024-40516 UPD | 6.5 | 8.8 | 0.0033 | 2024-07-16 |
CVE-2026-33875 | 6.5 | 9.3 | 0.0027 | 2026-03-27 |
CVE-2026-35643 | 6.5 | 8.8 | 0.0037 | 2026-04-10 |
CVE-2026-48745 | 6.5 | 9.3 | 0.0032 | 2026-06-17 |
CVE-2024-26131 UPD | 6.3 | 8.4 | 0.0047 | 2024-02-29 |
CVE-2025-23222 UPD | 6.2 | 8.4 | 0.0024 | 2025-01-24 |
CVE-2024-49579 UPD | 6.1 | 8.1 | 0.0042 | 2024-10-17 |
CVE-2026-40434 UPD | 6.0 | 8.1 | 0.0023 | 2026-04-17 |
CVE-2023-51440 UPD | 5.9 | 7.5 | 0.0060 | 2024-02-13 |
CVE-2025-13086 UPD | 5.9 | 7.5 | 0.0063 | 2025-12-03 |
CVE-2025-40820 UPD | 5.9 | 7.5 | 0.0048 | 2025-12-09 |
CVE-2019-25613 UPD | 5.9 | 7.5 | 0.0052 | 2026-03-22 |
CVE-2024-1621 UPD | 5.8 | 7.5 | 0.0036 | 2024-09-02 |
CVE-2026-44698 UPD | 5.6 | 8.3 | 0.0014 | 2026-05-29 |
CVE-2026-44894 UPD | 5.6 | 7.5 | 0.0014 | 2026-06-12 |
CVE-2026-6734 UPD | 5.6 | 7.5 | 0.0034 | 2026-06-17 |