CWE · MITRE source
CWE-340Generation of Predictable Numbers or Identifiers
The product uses a scheme that generates numbers or identifiers that are more predictable than required.
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: mostly · 9 mapping(s) from 6 framework(s): ATT&CK 3 (partial) · STIG oracle linux 8 2 (mostly) · STIG rhel 7 1 (mostly) · ASVS 5.0 1 (mostly) · STIG rhel 8 1 (partial) · OWASP-Web 1 (partial)
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 |
|---|---|---|---|
SC-12 | Cryptographic Key Establishment and Management | SC | Controlled key-establishment processes produce unpredictable key values instead of values derived from observable or guessable state. |
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-47945 | 7.0 | 9.8 | 0.0086 | 2024-10-15 |
CVE-2025-40925 | 7.0 | 9.1 | 0.0034 | 2025-09-20 |
CVE-2025-69286 | 7.0 | 9.8 | 0.0049 | 2025-12-31 |
CVE-2026-2439 | 7.0 | 9.8 | 0.0040 | 2026-02-16 |
CVE-2025-40926 | 7.0 | 9.8 | 0.0043 | 2026-03-05 |
CVE-2025-40931 | 7.0 | 9.1 | 0.0058 | 2026-03-05 |
CVE-2025-15604 | 7.0 | 9.8 | 0.0052 | 2026-03-28 |
CVE-2026-3256 UPD | 7.0 | 9.8 | 0.0053 | 2026-03-28 |
CVE-2026-5085 | 7.0 | 9.1 | 0.0034 | 2026-04-13 |
CVE-2026-40496 | 7.0 | 9.1 | 0.0040 | 2026-04-21 |
CVE-2026-5081 UPD | 7.0 | 9.1 | 0.0030 | 2026-05-06 |
CVE-2026-9733 | 7.0 | 9.1 | 0.0034 | 2026-06-23 |
CVE-2026-11374 | 7.0 | 9.0 | 0.0124 | 2026-06-23 |
CVE-2024-7558 | 5.5 | 8.7 | 0.0050 | 2024-10-02 |
CVE-2024-52299 | 5.5 | 7.5 | 0.0052 | 2024-11-13 |
CVE-2025-40923 UPD | 5.5 | 7.3 | 0.0033 | 2025-07-16 |
CVE-2025-40920 UPD | 5.5 | 8.6 | 0.0039 | 2025-08-11 |
CVE-2025-40933 | 5.5 | 7.5 | 0.0038 | 2025-09-17 |
CVE-2025-62294 | 5.5 | 7.5 | 0.0026 | 2025-11-20 |
CVE-2025-68701 | 5.5 | 7.5 | 0.0020 | 2026-01-13 |
CVE-2025-40932 | 5.5 | 8.2 | 0.0020 | 2026-02-27 |
CVE-2026-4269 | 5.5 | 7.5 | 0.0024 | 2026-03-16 |
CVE-2021-29480 | 3.5 | 4.4 | 0.0026 | 2021-06-29 |
CVE-2024-28957 | 3.5 | 5.3 | 0.0076 | 2024-04-15 |
CVE-2024-12034 | 3.5 | 5.3 | 0.0033 | 2024-12-24 |