CWE · MITRE source
CWE-1394Use of Default Cryptographic Key
The product uses a default cryptographic key for potentially critical functionality.
It is common practice for products to be designed to use default keys. The rationale is to simplify the manufacturing process or the system administrator's task of installation and deployment into an enterprise. However, if admins do not change the defaults, it is easier for attackers to bypass authentication quickly across multiple organizations.
Last updated: 04 July 2026 00:28 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: partial · 2 mapping(s) from 1 framework(s): ATT&CK 2 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
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-2024-29037 UPD | 7.0 | 9.1 | 0.0060 | 2024-03-20 |
CVE-2024-48956 | 7.0 | 9.8 | 0.0086 | 2024-12-09 |
CVE-2025-44954 UPD | 7.0 | 9.0 | 0.0068 | 2025-08-04 |
CVE-2025-55049 | 7.0 | 9.1 | 0.0028 | 2025-09-09 |
CVE-2025-41742 | 7.0 | 9.8 | 0.0043 | 2025-12-02 |
CVE-2025-41744 | 7.0 | 9.1 | 0.0037 | 2025-12-02 |
CVE-2023-6451 | 5.5 | 8.6 | 0.0053 | 2024-02-16 |
CVE-2026-5039 | 5.5 | 8.8 | 0.0013 | 2026-04-23 |
CVE-2024-11619 | 3.5 | 5.0 | 0.0070 | 2024-11-22 |
CVE-2025-26849 | 3.5 | 4.3 | 0.0023 | 2025-03-04 |
CVE-2025-1688 | 3.5 | 5.5 | 0.0019 | 2025-04-15 |
CVE-2026-20709 | 3.5 | 6.6 | 0.0011 | 2026-04-08 |
CVE-2024-10748 | 1.5 | 2.5 | 0.0026 | 2024-11-04 |
CVE-2026-25815 | 1.5 | 3.2 | 0.0011 | 2026-02-05 |
CVE-2026-2215 | 1.5 | 3.7 | 0.0027 | 2026-02-09 |