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: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (4)AI
| 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 | 4.1 | 9.8 | 0.0196 | 2025-10-20 |
CVE-2024-40515 | 2.4 | 9.8 | 0.0657 | 2024-07-16 |
CVE-2023-41094 | 2.0 | 10.0 | 0.0008 | 2023-10-04 |
CVE-2023-41355 | 2.0 | 9.8 | 0.0030 | 2023-11-03 |
CVE-2024-38886 | 2.0 | 9.8 | 0.0086 | 2024-08-02 |
CVE-2024-40516 | 1.9 | 8.8 | 0.0307 | 2024-07-16 |
CVE-2025-59159 | 1.9 | 9.6 | 0.0001 | 2025-10-06 |
CVE-2026-33875 | 1.9 | 9.3 | 0.0008 | 2026-03-27 |
CVE-2023-3663 | 1.8 | 8.8 | 0.0074 | 2023-08-03 |
CVE-2023-48387 | 1.8 | 8.8 | 0.0102 | 2023-12-15 |
CVE-2026-35643 | 1.8 | 8.8 | 0.0004 | 2026-04-10 |
CVE-2024-26131 | 1.7 | 8.4 | 0.0004 | 2024-02-29 |
CVE-2025-23222 | 1.7 | 8.4 | 0.0008 | 2025-01-24 |
CVE-2024-49579 | 1.6 | 8.1 | 0.0025 | 2024-10-17 |
CVE-2026-40434 | 1.6 | 8.1 | 0.0002 | 2026-04-17 |
CVE-2023-51440 | 1.5 | 7.5 | 0.0037 | 2024-02-13 |
CVE-2024-1621 | 1.5 | 7.5 | 0.0032 | 2024-09-02 |
CVE-2025-13086 | 1.5 | 7.5 | 0.0004 | 2025-12-03 |
CVE-2025-40820 | 1.5 | 7.5 | 0.0009 | 2025-12-09 |
CVE-2019-25613 | 1.5 | 7.5 | 0.0039 | 2026-03-22 |
CVE-2024-40503 | 1.4 | 6.5 | 0.0091 | 2024-07-16 |
CVE-2025-25305 | 1.4 | 7.0 | 0.0003 | 2025-02-18 |
CVE-2022-4800 | 1.3 | 6.5 | 0.0019 | 2022-12-28 |
CVE-2024-0009 | 1.3 | 6.3 | 0.0009 | 2024-02-14 |
CVE-2023-7004 | 1.3 | 6.5 | 0.0002 | 2024-03-15 |