CWE · MITRE source
CWE-759Use of a One-Way Hash without a Salt
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.
NIST 800-53 r5 controls that address this weakness (1)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AT-5 | Contacts with Security Groups and Associations | AT | Security 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 UPD | 6.5 | 9.1 | 0.0010 | 2026-05-28 |
CVE-2025-10205 UPD | 6.4 | 8.8 | 0.0022 | 2025-09-17 |
CVE-2025-34208 UPD | 5.8 | 7.5 | 0.0041 | 2025-10-02 |
CVE-2020-16244 UPD | 5.5 | 7.2 | 0.0065 | 2020-09-23 |
CVE-2023-1430 UPD | 5.3 | 6.5 | 0.0080 | 2023-06-09 |
CVE-2020-25164 UPD | 5.2 | 6.5 | 0.0061 | 2022-04-14 |
CVE-2024-36440 UPD | 5.2 | 6.8 | 0.0029 | 2024-08-22 |
CVE-2026-57263 | 4.9 | 6.8 | 0.0008 | 2026-08-11 |
CVE-2021-21253 UPD | 4.7 | 5.8 | 0.0074 | 2021-01-21 |
CVE-2025-36253 UPD | 4.5 | 5.9 | 0.0020 | 2026-02-02 |
CVE-2025-15544 | 4.5 | 5.9 | 0.0020 | 2026-08-03 |
CVE-2025-15631 | 4.5 | 5.9 | 0.0018 | 2026-08-03 |
CVE-2026-45027 UPD | 4.4 | 5.9 | 0.0014 | 2026-05-27 |
CVE-2025-53884 UPD | 4.2 | 5.3 | 0.0017 | 2025-09-17 |
CVE-2024-8453 | 3.9 | 4.9 | 0.0031 | 2024-09-30 |
CVE-2025-27408 UPD | 3.7 | 4.8 | 0.0015 | 2025-02-28 |
CVE-2023-33838 UPD | 3.5 | 4.4 | 0.0024 | 2025-01-29 |
CVE-2026-9370 UPD | 3.1 | 3.7 | 0.0020 | 2026-05-24 |