CWE · MITRE source
CWE-1391Use of Weak Credentials
The product uses weak credentials (such as a default key or hard-coded password) that can be calculated, derived, reused, or guessed by an attacker.
By design, authentication protocols try to ensure that attackers must perform brute force attacks if they do not know the credentials such as a key or password. However, when these credentials are easily predictable or even fixed (as with default or hard-coded passwords and keys), then the attacker can defeat the mechanism without relying on brute force. Credentials may be weak for different reasons, such as: Even if a new, unique credential is intended to be generated for each product installation, if the generation is predictable, then that may also simplify guessing attacks.
Last updated: 20 August 2026 13:14 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: mostly · 11 mapping(s) from 4 framework(s): CSF 2.0 6 (mostly) · STIG oracle linux 8 3 (partial) · STIG rhel 7 1 (partial) · STIG rhel 8 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
- 7 hardening rules · 3 OS baselines
V6.2.2V6.3.1V6.3.2V6.4.2
NIST 800-53 r5 controls that address this weakness (2)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
IA-5 | Authenticator Management | IA | Ensuring sufficient strength of mechanism for authenticators prevents use of weak credentials. |
IA-7 | Cryptographic Module Authentication | IA | Enforces use of credentials that comply with standards rather than weak credentials for module access. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-51978 UPD | 8.5 | 9.8 | 0.1915 | 2025-06-25 |
CVE-2024-12728 UPD | 7.5 | 9.8 | 0.0095 | 2024-12-19 |
CVE-2025-6077 UPD | 7.4 | 9.8 | 0.0069 | 2025-08-02 |
CVE-2024-43698 UPD | 7.3 | 9.8 | 0.0044 | 2024-10-22 |
CVE-2025-30519 UPD | 7.3 | 9.8 | 0.0044 | 2025-09-18 |
CVE-2026-22886 UPD | 7.3 | 9.8 | 0.0040 | 2026-03-03 |
CVE-2025-67114 | 7.3 | 9.8 | 0.0052 | 2026-03-19 |
CVE-2026-39920 | 7.3 | 9.8 | 0.0054 | 2026-04-24 |
CVE-2025-53558 UPD | 6.8 | 8.8 | 0.0135 | 2025-07-31 |
CVE-2026-44351 UPD | 6.7 | 9.1 | 0.0024 | 2026-05-13 |
CVE-2026-45363 | 6.7 | 9.1 | 0.0024 | 2026-07-14 |
CVE-2024-28066 UPD | 6.6 | 8.8 | 0.0045 | 2024-04-08 |
CVE-2024-29071 UPD | 6.5 | 8.8 | 0.0036 | 2024-03-25 |
CVE-2024-7558 UPD | 6.2 | 8.7 | 0.0050 | 2024-10-02 |
CVE-2023-31240 UPD | 6.1 | 8.3 | 0.0054 | 2023-05-22 |
CVE-2026-23853 UPD | 6.1 | 8.4 | 0.0016 | 2026-04-17 |
CVE-2022-3010 UPD | 5.9 | 7.5 | 0.0058 | 2024-01-02 |
CVE-2023-48257 UPD | 5.9 | 7.8 | 0.0054 | 2024-01-10 |
CVE-2024-45272 UPD | 5.9 | 7.5 | 0.0062 | 2024-10-15 |
CVE-2024-45722 | 5.9 | 7.5 | 0.0047 | 2024-12-06 |
CVE-2025-52364 UPD | 5.9 | 7.5 | 0.0051 | 2025-07-09 |
CVE-2023-0635 UPD | 5.8 | 7.8 | 0.0037 | 2023-06-05 |
CVE-2025-35970 UPD | 5.8 | 7.5 | 0.0045 | 2025-08-07 |
CVE-2025-59460 UPD | 5.8 | 7.5 | 0.0040 | 2025-10-27 |
CVE-2026-22910 UPD | 5.8 | 7.5 | 0.0044 | 2026-01-15 |