CWE · MITRE source
CWE-757Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')
A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.
When a security mechanism can be forced to downgrade to use a less secure algorithm, this can make it easier for attackers to compromise the product by exploiting weaker algorithm. The victim might not be aware that the less secure algorithm is being used. For example, if an attacker can force a communications channel to use cleartext instead of strongly-encrypted data, then the attacker could read the channel by sniffing, instead of going through extra effort of trying to decrypt the data using brute force techniques.
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: full · 19 mapping(s) from 9 framework(s): ASVS 5.0 8 (mostly) · CAPEC 3 (partial) · ATT&CK 2 (full) · STIG windows 10 1 (full) · OWASP-Web 1 (full) · STIG windows 11 1 (mostly) · STIG windows server 2016 1 (mostly) · STIG windows server 2019 1 (mostly) · STIG windows server 2022 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A04:2025 Cryptographic Failures.
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-2019-14887 | 7.0 | 9.1 | 0.0107 | 2020-03-16 |
CVE-2024-38883 | 7.0 | 9.1 | 0.0041 | 2024-08-02 |
CVE-2024-4995 | 7.0 | 9.8 | 0.0091 | 2024-12-18 |
CVE-2025-24154 | 7.0 | 9.1 | 0.0113 | 2025-01-27 |
CVE-2017-9269 | 5.5 | 7.7 | 0.0229 | 2018-03-01 |
CVE-2018-25029 | 5.5 | 8.1 | 0.0062 | 2022-02-04 |
CVE-2022-23000 | 5.5 | 7.3 | 0.0019 | 2022-07-25 |
CVE-2024-23656 UPD | 5.5 | 7.5 | 0.0043 | 2024-01-25 |
CVE-2026-32650 | 5.5 | 7.5 | 0.0021 | 2026-04-17 |
CVE-2017-9267 | 3.5 | 6.5 | 0.0105 | 2018-03-02 |
CVE-2019-16791 | 3.5 | 6.9 | 0.0067 | 2020-01-22 |
CVE-2020-10135 | 3.5 | 5.4 | 0.0239 | 2020-05-19 |
CVE-2020-16200 | 3.5 | 6.5 | 0.0058 | 2020-09-18 |
CVE-2021-36326 | 3.5 | 6.5 | 0.0118 | 2021-11-30 |
CVE-2023-2974 | 3.5 | 6.5 | 0.0088 | 2023-07-04 |
CVE-2024-20069 | 3.5 | 6.5 | 0.0057 | 2024-06-03 |
CVE-2025-36582 UPD | 3.5 | 4.8 | 0.0022 | 2025-07-01 |
CVE-2026-2673 UPD | 3.5 | 6.5 | 0.0043 | 2026-03-13 |
CVE-2026-6550 | 3.5 | 4.7 | 0.0010 | 2026-04-20 |
CVE-2026-1677 UPD | 3.5 | 5.3 | 0.0020 | 2026-05-11 |
CVE-2026-6092 | 3.5 | 5.3 | 0.0021 | 2026-06-25 |
CVE-2022-33160 | 1.5 | 3.7 | 0.0028 | 2023-10-06 |
CVE-2025-59270 | 1.5 | 3.1 | 0.0022 | 2025-09-16 |