CWE · MITRE source
CWE-324Use of a Key Past its Expiration Date
The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key.
While the expiration of keys does not necessarily ensure that they are compromised, it is a significant concern that keys which remain in use for prolonged periods of time have a decreasing probability of integrity. For this reason, it is important to replace keys within a period of time proportional to their strength.
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 · 2 mapping(s) from 2 framework(s): OWASP-Web 1 (mostly) · ATT&CK 1 (mostly)
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 | Key-management requirements enforce lifecycle controls that prevent continued use of expired or superseded keys. |
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-36031 | 7.0 | 9.8 | 0.0075 | 2024-05-30 |
CVE-2022-35401 | 6.0 | 8.1 | 0.2085 | 2023-01-10 |
CVE-2021-33020 | 5.5 | 8.2 | 0.0060 | 2022-04-01 |
CVE-2025-31123 | 5.5 | 8.7 | 0.0037 | 2025-03-31 |
CVE-2025-2291 | 5.5 | 8.1 | 0.0031 | 2025-04-16 |
CVE-2019-3790 | 3.5 | 6.1 | 0.0066 | 2019-06-06 |
CVE-2022-24732 | 3.5 | 6.3 | 0.0039 | 2022-03-09 |
CVE-2022-2447 | 3.5 | 6.6 | 0.0061 | 2022-09-01 |
CVE-2024-25679 UPD | 3.5 | 6.5 | 0.0025 | 2024-02-09 |
CVE-2024-31893 | 3.5 | 4.3 | 0.0026 | 2024-05-22 |
CVE-2024-31894 | 3.5 | 4.3 | 0.0026 | 2024-05-22 |
CVE-2024-31895 | 3.5 | 4.3 | 0.0027 | 2024-05-22 |
CVE-2024-38277 | 3.5 | 5.4 | 0.0024 | 2024-06-18 |
CVE-2024-6299 | 3.5 | 4.8 | 0.0016 | 2024-06-25 |
CVE-2024-7318 | 3.5 | 4.8 | 0.0039 | 2024-09-09 |
CVE-2023-5342 | 3.5 | 4.1 | 0.0008 | 2025-08-14 |
CVE-2025-48813 | 3.5 | 6.3 | 0.0023 | 2025-10-14 |
CVE-2025-33012 | 3.5 | 6.3 | 0.0014 | 2025-11-07 |
CVE-2025-13723 | 3.5 | 5.3 | 0.0017 | 2026-03-13 |
CVE-2026-52809 | 3.5 | 6.8 | 0.0020 | 2026-06-24 |