Cyber Resilience

CWE · MITRE source

CWE-327Use of a Broken or Risky Cryptographic Algorithm

Abstraction: Class · CVEs in our corpus: 677

The product uses a broken or risky cryptographic algorithm or protocol.

Cryptographic algorithms are the methods by which data is scrambled to prevent observation or influence by unauthorized actors. Insecure cryptography can be exploited to expose sensitive information, modify data in unexpected ways, spoof identities of other users or devices, or other impacts. It is very difficult to produce a secure algorithm, and even high-profile algorithms by accomplished cryptographic experts have been broken. Well-known techniques exist to break or weaken various kinds of cryptography. Accordingly, there are a small number of well-understood and heavily studied algorithms that should be used by most products. Using a non-standard or known-insecure algorithm is dangerous because a determined adversary may be able to break the algorithm and compromise whatever data has been protected. Since the state of cryptography advances so rapidly, it is common for an algorithm to be considered "unsafe" even if it was once thought to be strong. This can happen when new attacks are discovered, or if computing power increases so much that the cryptographic algorithm no longer provides the amount of protection that was originally thought. For a number of reasons, this weakness is even more challenging to manage with hardware deployment of cryptographic algorithms as opposed to software implementation. First, if a flaw is discovered with hardware-implemented cryptography, the flaw cannot be fixed in most cases without a recall of the product, because hardware is not easily replaceable like software. Second, because the hardware product is expected to work for years, the adversary's computing power will only increase over time.

Last updated: 04 July 2026 08:17 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 · 17 mapping(s) from 10 framework(s): CAPEC 7 (partial) · ATT&CK 2 (partial) · STIG windows 10 1 (full) · STIG windows server 2019 1 (full) · STIG windows server 2022 1 (full) · OWASP-Web 1 (full) · STIG oracle linux 8 1 (mostly) · STIG windows 11 1 (mostly) · STIG windows server 2016 1 (mostly) · CSF 2.0 1 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A04:2025 Cryptographic Failures.

NIST 800-53 r5 controls that address this weakness (9)AI

Control Title Family Why it addresses this CWE
PM-15Security and Privacy Groups and AssociationsPMOngoing education and sharing of recommended practices helps organizations identify and migrate away from broken or risky cryptographic algorithms.
PM-16Threat Awareness ProgramPMCross-organization threat feeds commonly include advances in cryptanalysis and active exploits against weak or broken algorithms, allowing organizations to deprecate them proactively.
PM-3Information Security and Privacy ResourcesPMCapital planning and funding allow selection and ongoing support of strong cryptographic algorithms rather than weak or broken ones.
RA-4Risk Assessment UpdateRARisk updates surface newly-broken or risky cryptographic algorithms as threat intelligence and computing advances evolve, enabling timely replacement.
RA-5Vulnerability Monitoring and ScanningRAScanners flag use of broken or weak cryptographic algorithms via known-vulnerability databases.
SI-2Flaw RemediationSIFlaw remediation replaces broken or risky cryptographic algorithms once safer implementations are released by vendors.
SI-5Security Alerts, Advisories, and DirectivesSISecurity alerts and directives routinely identify broken or risky cryptographic algorithms and require their replacement within defined time frames.
AT-5Contacts with Security Groups and AssociationsATContacts with security groups provide timely information on broken or risky cryptographic algorithms, reducing the likelihood of their selection and use.
SC-13Cryptographic ProtectionSCEnforces approved cryptographic algorithms for each use case, blocking use of broken or risky algorithms.

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-2015-28088.03.70.74012015-04-01
CVE-2016-66028.09.80.54792017-01-23
CVE-2023-340398.09.80.63952023-08-29
CVE-2007-60137.09.80.03282007-11-19
CVE-2017-49177.09.80.00652017-06-07
CVE-2014-86877.09.80.43812017-06-08
CVE-2017-94667.09.80.00492017-06-26
CVE-2017-98597.09.80.01132017-08-05
CVE-2014-99697.09.80.00422017-08-18
CVE-2012-44497.09.80.01202017-10-30
CVE-2017-177177.09.80.00712017-12-17
CVE-2017-178787.09.80.01602017-12-27
CVE-2015-92357.09.80.08662018-05-29
CVE-2019-94837.09.10.00592019-03-01
CVE-2019-01877.09.80.02712019-03-06
CVE-2019-59197.09.10.00952019-03-12
CVE-2019-57237.09.80.01082019-03-21
CVE-2019-55027.09.10.00912019-08-05
CVE-2019-50357.09.00.00422019-08-20
CVE-2019-161437.09.80.00932019-09-09
CVE-2019-82377.09.80.02802019-10-23
CVE-2019-90957.09.80.00752020-03-11
CVE-2018-210587.09.80.00272020-04-08
CVE-2020-103777.09.80.00542020-04-17
CVE-2019-130227.09.80.01312020-05-14