CWE · MITRE source
CWE-295Improper Certificate Validation
The product does not validate, or incorrectly validates, a certificate.
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: full · 12 mapping(s) from 6 framework(s): STIG oracle linux 8 3 (full) · ATT&CK 3 (mostly) · STIG rhel 7 2 (mostly) · STIG rhel 8 2 (mostly) · CAPEC 1 (partial) · OWASP-Web 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
NIST 800-53 r5 controls that address this weakness (3)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-17 | Public Key Infrastructure Certificates | SC | Mandates approved trust anchors and issuance policies, directly preventing acceptance of unvalidated or untrusted certificates. |
SC-45 | System Time Synchronization | SC | Correct system time is required for proper enforcement of certificate notBefore/notAfter dates and time-based revocation checks. |
SA-19 | Component Authenticity | SA | When certificates are used to establish component provenance, the control requires correct certificate validation procedures. |
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-2020-0601 KEV | 10.0 | 8.1 | 0.8944 | 2020-01-14 |
CVE-2022-20703 KEV | 10.0 | 10.0 | 0.0920 | 2022-02-10 |
CVE-2022-26923 KEV | 10.0 | 8.8 | 0.8328 | 2022-05-10 |
CVE-2023-20963 KEV | 10.0 | 7.8 | 0.0144 | 2023-03-24 |
CVE-2023-41991 KEV | 10.0 | 5.5 | 0.0455 | 2023-09-21 |
CVE-2009-3555 | 8.0 | 9.8 | 0.8726 | 2009-11-09 |
CVE-2015-4000 | 8.0 | 3.7 | 0.9986 | 2015-05-21 |
CVE-2023-27823 | 8.0 | 9.8 | 0.5252 | 2023-05-12 |
CVE-2010-1378 | 7.0 | 9.8 | 0.0127 | 2010-11-15 |
CVE-2015-7826 | 7.0 | 9.8 | 0.0112 | 2017-04-10 |
CVE-2017-2800 | 7.0 | 9.8 | 0.0853 | 2017-05-24 |
CVE-2017-7406 | 7.0 | 9.8 | 0.0069 | 2017-07-07 |
CVE-2015-3886 | 7.0 | 9.8 | 0.0173 | 2017-07-21 |
CVE-2015-2320 | 7.0 | 9.8 | 0.0354 | 2018-01-08 |
CVE-2017-17301 | 7.0 | 9.8 | 0.0099 | 2018-02-15 |
CVE-2018-9127 | 7.0 | 9.8 | 0.0096 | 2018-04-02 |
CVE-2018-4991 | 7.0 | 9.8 | 0.0578 | 2018-05-19 |
CVE-2018-12829 | 7.0 | 9.8 | 0.0507 | 2018-08-29 |
CVE-2016-1000030 | 7.0 | 9.8 | 0.0184 | 2018-09-05 |
CVE-2018-15387 | 7.0 | 9.8 | 0.0110 | 2018-10-05 |
CVE-2019-6266 | 7.0 | 9.8 | 0.0120 | 2019-02-25 |
CVE-2019-6592 | 7.0 | 9.1 | 0.0104 | 2019-02-26 |
CVE-2018-11747 | 7.0 | 9.8 | 0.0072 | 2019-03-21 |
CVE-2019-8351 | 7.0 | 9.1 | 0.0131 | 2019-03-21 |
CVE-2018-5926 | 7.0 | 9.1 | 0.0117 | 2019-03-27 |