CWE · MITRE source
CWE-322Key Exchange without Entity Authentication
The product performs a key exchange with an actor without verifying the identity of that actor.
Performing a key exchange will preserve the integrity of the information sent between two entities, but this will not guarantee that the entities are who they claim they are. This may enable an attacker to impersonate an actor by modifying traffic between the two entities. Typically, this involves a victim client that contacts a malicious server that is impersonating a trusted server. If the client skips authentication or ignores an authentication failure, the malicious server may request authentication information from the user. The malicious server can then use this authentication information to log in to the trusted server using the victim's credentials, sniff traffic between the victim and trusted server, etc.
Last updated: 16 October 2026 00:29 UTC
OWASP Top 10 for Web (2025)
This weakness contributes to A04:2025 Cryptographic Failures.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
PR.AA-02PR.AA-03PR.AA-04SC-12Cryptographic Key Establishment and Management
—
—
V12.1.3
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-1709 UPD | 7.7 | 9.4 | 0.0579 | 2026-02-06 |
CVE-2022-39251 UPD | 6.5 | 8.6 | 0.0118 | 2022-09-28 |
CVE-2022-39250 UPD | 6.5 | 8.6 | 0.0118 | 2022-09-29 |
CVE-2022-39248 UPD | 6.4 | 8.6 | 0.0100 | 2022-09-28 |
CVE-2022-39255 UPD | 6.4 | 8.6 | 0.0103 | 2022-09-28 |
CVE-2022-39252 UPD | 6.3 | 8.6 | 0.0062 | 2022-09-29 |
CVE-2022-39254 UPD | 6.3 | 8.6 | 0.0066 | 2022-09-29 |
CVE-2026-45361 UPD | 6.3 | 8.1 | 0.0080 | 2026-05-25 |
CVE-2024-47519 UPD | 6.2 | 8.3 | 0.0034 | 2025-01-10 |
CVE-2025-20163 UPD | 6.2 | 8.7 | 0.0043 | 2025-06-04 |
CVE-2026-58065 UPD | 6.2 | 8.1 | 0.0074 | 2026-07-13 |
CVE-2022-39249 UPD | 6.1 | 7.5 | 0.0128 | 2022-09-28 |
CVE-2025-62501 UPD | 6.1 | 8.1 | 0.0050 | 2026-02-03 |
CVE-2025-13914 UPD | 6.1 | 8.7 | 0.0030 | 2026-04-09 |
CVE-2022-39246 UPD | 6.0 | 7.5 | 0.0087 | 2022-09-28 |
CVE-2022-39257 UPD | 6.0 | 7.5 | 0.0100 | 2022-09-28 |
CVE-2021-34433 UPD | 5.8 | 7.5 | 0.0034 | 2021-08-20 |
CVE-2024-6572 UPD | 5.6 | 7.4 | 0.0034 | 2024-09-09 |
CVE-2024-4871 UPD | 5.3 | 6.8 | 0.0061 | 2024-05-14 |
CVE-2024-7516 UPD | 5.3 | 7.1 | 0.0025 | 2024-11-12 |
CVE-2026-44467 UPD | 5.1 | 6.8 | 0.0022 | 2026-05-13 |
CVE-2026-33697 UPD | 5.0 | 7.5 | 0.0007 | 2026-03-27 |
CVE-2026-18654 | 4.9 | 6.8 | 0.0029 | 2026-08-03 |
CVE-2026-1354 | 4.7 | 6.4 | 0.0013 | 2026-04-21 |
CVE-2026-77703 | 4.5 | 5.9 | 0.0024 | 2026-09-24 |