Class weakness

Draft

CWE-326: Inadequate Encryption Strength

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.

Last updated May 1, 2026

165

Recorded CVEs

With this primary weakness

4

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Class

Abstraction

MITRE classification

Overview

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

Real-world CVEs

165 recorded CVEs are caused by CWE-326 (Inadequate Encryption Strength), including 4 in CISA's KEV (Known Exploited Vulnerabilities) catalog. KEVs are shown first. 14 new CWE-326 CVEs have been recorded so far in 2026 (30 in 2025).

Showing 12 of 165 recorded CWE-326 CVEs. Track new ones as they are published and get AI-written analysis and fixes.

Monitor CWE-326 vulnerabilities

Common consequences

What can happen when CWE-326 is exploited.

Bypass Protection Mechanism, Read Application Data

Affects: Access Control, Confidentiality

An attacker may be able to decrypt the data using brute force attacks.

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Architecture and Design

How to prevent it

Practical mitigations for CWE-326, grouped by where in the lifecycle they apply.

Architecture and Design

Use an encryption scheme that is currently considered to be strong by experts in the field.

How to detect it

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.)

Effectiveness: High

Illustrative examples

Real CVEs that MITRE cites as examples of this weakness.

CVE-2001-1546 — Weak encryption
CVE-2004-2172 — Weak encryption (chosen plaintext attack)
CVE-2002-1682 — Weak encryption
CVE-2002-1697 — Weak encryption produces same ciphertext from the same plaintext blocks.
CVE-2002-1739 — Weak encryption
CVE-2005-2281 — Weak encryption scheme
CVE-2002-1872 — Weak encryption (XOR)
CVE-2002-1910 — Weak encryption (reversible algorithm).
CVE-2002-1946 — Weak encryption (one-to-one mapping).
CVE-2002-1975 — Encryption error uses fixed salt, simplifying brute force / dictionary attacks (overlaps randomness).

Terminology & mappings

Mapped taxonomies

PLOVER: Weak Encryption
OWASP Top Ten 2007: Insecure Cryptographic Storage (A8) — CWE More Specific fit
OWASP Top Ten 2007: Insecure Communications (A9) — CWE More Specific fit
OWASP Top Ten 2004: Insecure Storage (A8) — CWE More Specific fit

Attack patterns

CAPEC attack patterns that exploit this weakness.

Frequently asked questions

Common questions about CWE-326.

What is CWE-326?

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.

What CVEs are caused by CWE-326?

165 recorded CVEs are attributed to CWE-326, including CVE-2018-18325, CVE-2018-15811, CVE-2017-1000486. 4 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.

Is CWE-326 part of the OWASP Top 10?

CWE-326 maps to OWASP Top Ten 2007: Insecure Cryptographic Storage (A8) in the OWASP security taxonomy.

How do you prevent CWE-326?

Use an encryption scheme that is currently considered to be strong by experts in the field.

How is CWE-326 detected?

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.)

What are the consequences of CWE-326?

Exploiting CWE-326 can lead to: Bypass Protection Mechanism, Read Application Data.

Is CWE-326 actively exploited?

Yes. 4 CWE-326 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 165 recorded CVEs.

References

Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.

Stay ahead of CWE-326

Get alerted the moment a new CWE-326 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.

Start free See pricing

Real-world CVEs

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

How to prevent it

How to detect it

Automated Static Analysis

Illustrative examples

Related weaknesses

Parent

Child

Terminology & mappings

Mapped taxonomies

Attack patterns

Frequently asked questions

What is CWE-326?

What CVEs are caused by CWE-326?

Is CWE-326 part of the OWASP Top 10?

How do you prevent CWE-326?

How is CWE-326 detected?

What are the consequences of CWE-326?

Is CWE-326 actively exploited?

References

Stay ahead of CWE-326