Cyber Resilience

CWE · MITRE source

CWE-759Use of a One-Way Hash without a Salt

Abstraction: Variant · CVEs in our corpus: 19

The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of the input.

This makes it easier for attackers to pre-compute the hash value using dictionary attack techniques such as rainbow tables. It should be noted that, despite common perceptions, the use of a good salt with a hash does not sufficiently increase the effort for an attacker who is targeting an individual password, or who has a large amount of computing resources available, such as with cloud-based services or specialized, inexpensive hardware. Offline password cracking can still be effective if the hash function is not expensive to compute; many cryptographic functions are designed to be efficient and can be vulnerable to attacks using massive computing resources, even if the hash is cryptographically strong. The use of a salt only slightly increases the computing requirements for an attacker compared to other strategies such as adaptive hash functions. See CWE-916 for more details.

Last updated: 20 August 2026 13:14 UTC

OWASP Top 10 for Web (2025)

This weakness contributes to A04:2025 Cryptographic Failures.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • AT-5 Contacts with Security Groups and Associations
  • PR.DS-01
  • PR.PS-06
  • SC-13 Cryptographic Protection
Detect
Catch it (CSF Detect / Respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

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

Control Title Family Why it addresses this CWE
AT-5Contacts with Security Groups and AssociationsATSecurity associations provide guidance on proper one-way hash usage including salting, reducing the chance of unsalted implementations.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2026-45787 6.59.10.00102026-05-28
CVE-2025-10205 6.48.80.00222025-09-17
CVE-2025-34208 5.87.50.00412025-10-02
CVE-2020-16244 5.57.20.00652020-09-23
CVE-2023-1430 5.36.50.00802023-06-09
CVE-2020-25164 5.26.50.00612022-04-14
CVE-2024-36440 5.26.80.00292024-08-22
CVE-2026-572634.96.80.00082026-08-11
CVE-2021-21253 4.75.80.00742021-01-21
CVE-2025-36253 4.55.90.00202026-02-02
CVE-2025-155444.55.90.00202026-08-03
CVE-2025-156314.55.90.00182026-08-03
CVE-2026-45027 4.45.90.00142026-05-27
CVE-2025-53884 4.25.30.00172025-09-17
CVE-2024-84533.94.90.00312024-09-30
CVE-2025-27408 3.74.80.00152025-02-28
CVE-2023-33838 3.54.40.00242025-01-29
CVE-2026-9370 3.13.70.00202026-05-24