CWE-326: Inadequate Encryption Strength

ClassDraft

The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.

View on MITRE
Back to CWE Lookup

Extended Description

A weak encryption scheme can be subjected to brute force attacks that have a reasonable chance of succeeding using current attack methods and resources.

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-326 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-326, Inadequate Encryption Strength, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Inadequate Encryption Strength during Architecture and Design

MITRE associates mitigation with Architecture and Design; documented detection approaches include Automated Static Analysis; recorded impacts include Bypass Protection Mechanism, and Read Application Data. Use these source-defined anchors to turn CWE-326 into implementation, review, and verification checks for the affected component.

CWE-326: Inadequate Encryption Strength — MITRE CWE

Triage CWE-326 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-326, Inadequate Encryption Strength, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-326

Apply MITRE's full root-cause mapping guidance when using CWE-326, Inadequate Encryption Strength. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-326 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-326, Inadequate Encryption Strength. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-326: Inadequate Encryption Strength?+

CWE-326: Inadequate Encryption Strength is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. A weak encryption scheme can be subjected to brute force attacks that have a reasonable chance of succeeding using current attack methods and resources.

What are the security consequences of Inadequate Encryption Strength?+

If exploited, CWE-326 (Inadequate Encryption Strength) it can compromise Access Control and Confidentiality, leading to outcomes such as Bypass Protection Mechanism and Read Application Data.

How do you prevent or mitigate Inadequate Encryption Strength?+

Recommended mitigations for CWE-326 include: Use an encryption scheme that is currently considered to be strong by experts in the field.

Which programming languages are affected by Inadequate Encryption Strength?+

CWE-326 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Inadequate Encryption Strength?+

MITRE documents real CVEs mapped to CWE-326, including CVE-2001-1546, CVE-2004-2172, CVE-2002-1682, CVE-2002-1697 and CVE-2002-1739. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-326 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-326

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement