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: 04 July 2026 08:17 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: full · 4 mapping(s) from 2 framework(s): ATT&CK 3 (mostly) · OWASP-Web 1 (full)
OWASP Top 10 for Web (2025)
This weakness contributes to A04:2025 Cryptographic Failures.
NIST 800-53 r5 controls that address this weakness (1)AI
| 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. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-45787 UPD | 7.0 | 9.1 | 0.0010 | 2026-05-28 |
CVE-2020-16244 | 5.5 | 7.2 | 0.0065 | 2020-09-23 |
CVE-2025-10205 | 5.5 | 8.8 | 0.0020 | 2025-09-17 |
CVE-2025-34208 | 5.5 | 7.5 | 0.0041 | 2025-10-02 |
CVE-2021-21253 | 3.5 | 5.8 | 0.0074 | 2021-01-21 |
CVE-2020-25164 | 3.5 | 6.5 | 0.0060 | 2022-04-14 |
CVE-2023-1430 | 3.5 | 6.5 | 0.0080 | 2023-06-09 |
CVE-2024-36440 | 3.5 | 6.8 | 0.0029 | 2024-08-22 |
CVE-2024-8453 | 3.5 | 4.9 | 0.0030 | 2024-09-30 |
CVE-2023-33838 | 3.5 | 4.4 | 0.0023 | 2025-01-29 |
CVE-2025-27408 | 3.5 | 4.8 | 0.0015 | 2025-02-28 |
CVE-2025-53884 | 3.5 | 5.3 | 0.0016 | 2025-09-17 |
CVE-2025-36253 | 3.5 | 5.9 | 0.0020 | 2026-02-02 |
CVE-2026-45027 UPD | 3.5 | 5.9 | 0.0014 | 2026-05-27 |
CVE-2026-9370 UPD | 1.5 | 3.7 | 0.0020 | 2026-05-24 |