What is CWE-757?
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.
CWE-757 is a base-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Language: Not Language-Specific.
Source: MITRE CWE (CWE-757 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.
Consequences
- Access Control — Bypass Protection Mechanism
Source: MITRE CWE, common consequences.
How CWE-757 is exploited in the wild
Threadlinqs maps 4 CVEs to CWE-757, published between 2026-06-25 and 2026-10-07. None of them is in the CISA KEV catalog yet. By CVSS v3 severity the set splits into 1 medium, 1 low. The highest EPSS score in the set is 0.3% (CVE-2026-107279), the modelled probability of exploitation in the next 30 days. 1 tracked threat references CWE-757 directly or through a CVE it covers; the most recent is “25 Zero-Knowledge Bypass Vulnerabilities in Cloud Password Managers (Bitwarden/LastPass/Dashlane) — ETH Zurich Research, Key Escrow, AES-CBC Malleability, KDF Downgrade (300Kx Brute-Force), Unauthenticated Public Keys, 60M+ Users” (2026-02-17). Affected products concentrate in AsyncHttpClient (2), CoreWCF (1), wolfSSL (1).
Vulnerabilities (CVEs)
All 4 CVEs mapped to CWE-757, CISA KEV first, then by CVSS score.
- CVE-2026-6092 — CVSS 5.3 medium · EPSS 0.1% · published 2026-06-25
- CVE-2026-54780 — CVSS 3.7 low · EPSS 0.1% · published 2026-07-08
- CVE-2026-107279 — EPSS 0.3% · published 2026-10-07
- CVE-2026-107231 — EPSS 0.2% · published 2026-10-07
Affected vendors
- AsyncHttpClient — 2 CVEs
- CoreWCF — 1 CVE
- wolfSSL — 1 CVE
Threat activity
1 tracked threat cite CWE-757:
Detection methods (MITRE CWE)
- Automated Static Analysis (effectiveness: High): Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.