Threadlinqs IntelligenceStart free

Weakness · VariantCWE-321

CWE-321: Use of Hard-coded Cryptographic Key

Likelihood of exploit: HighKEV-linkedVariant

As of 2026-11-19, CWE-321 (Use of Hard-coded Cryptographic Key) underlies 21 CVEs tracked by Threadlinqs, 2 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 30 tracked threats. MITRE rates its likelihood of exploit as High.

CVEs
21Mapped to CWE-321
CISA KEV
2Exploited in the wild
Critical
8CVSS v3 critical CVEs
Threats
30Tracked campaigns citing it
Likelihood
HighMITRE likelihood of exploit

Last updated:

What is CWE-321?

The product uses a hard-coded, unchangeable cryptographic key.

CWE-321 is a variant-level weakness in MITRE’s Common Weakness Enumeration, with a MITRE likelihood of exploit of High. Applicable platforms: Not Language-Specific; ICS/OT.

Source: MITRE CWE (CWE-321 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.

Consequences

  • Access Control — Bypass Protection Mechanism, Gain Privileges or Assume Identity, Read Application Data. If hard-coded cryptographic keys are used, it is almost certain that malicious users will gain access through the account in question. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.

Source: MITRE CWE, common consequences.

How CWE-321 is exploited in the wild

Threadlinqs maps 21 CVEs to CWE-321, published between 2016-06-07 and 2026-11-10. 2 are listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild. By CVSS v3 severity the set splits into 8 critical, 5 high, 3 medium. The highest EPSS score in the set is 94.3% (CVE-2025-30406), the modelled probability of exploitation in the next 30 days. 30 tracked threats reference CWE-321 directly or through a CVE it covers; the most recent is “BOSSAI: AI-Augmented Multi-Agent Attack Campaign Exposes Taiwan Emergency Dispatch and Patient Records” (2026-11-05). Affected products concentrate in Apache Software Foundation (3), TP-Link Systems Inc. (2), AMD (1), among 19 vendors in total.

Vulnerabilities (CVEs)

All 21 CVEs mapped to CWE-321, CISA KEV first, then by CVSS score.

Affected vendors

Threat activity

30 tracked threats cite CWE-321; the 25 most recent are listed.

Mitigations

  • Architecture and Design: Prevention schemes mirror that of hard-coded password storage.

Source: MITRE CWE, potential mitigations.

Detection methods (MITRE CWE)

  • Automated Static Analysis: 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.