CWE · MITRE source
CWE-187Partial String Comparison
The product performs a comparison that only examines a portion of a factor before determining whether there is a match, such as a substring, leading to resultant weaknesses.
For example, an attacker might succeed in authentication by providing a small password that matches the associated portion of the larger, correct password.
Last updated: 19 November 2026 23:37 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 · 19 mapping(s) from 5 framework(s): ATT&CK 10 (full) · ISO_IEC_27002_2022 3 (mostly) · 800-53 3 (mostly) · 2 (mostly) · ASVS 5.0 1 (full)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| 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).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-41110 UPD | 8.1 | 9.9 | 0.1650 | 2024-07-24 |
CVE-2022-31802 UPD | 7.6 | 9.8 | 0.0135 | 2022-06-24 |
CVE-2026-115646 | 7.3 | 9.8 | 0.0039 | 2026-11-10 |
CVE-2026-35031 UPD | 7.1 | 9.9 | 0.0077 | 2026-04-14 |
CVE-2024-39742 UPD | 6.2 | 8.1 | 0.0076 | 2024-07-08 |
CVE-2026-55602 UPD | 6.2 | 8.6 | 0.0038 | 2026-06-22 |
CVE-2026-94576 | 6.0 | 8.0 | 0.0043 | 2026-10-08 |
CVE-2026-30874 | 5.8 | 7.8 | 0.0033 | 2026-03-19 |
CVE-2026-34785 UPD | 5.8 | 7.5 | 0.0040 | 2026-04-02 |
CVE-2026-87853 UPD | 5.7 | 7.5 | 0.0044 | 2026-09-09 |
CVE-2026-62750 | 5.2 | 6.5 | 0.0068 | 2026-08-11 |
CVE-2026-101914 | 4.9 | 6.5 | 0.0025 | 2026-09-28 |
CVE-2026-44837 UPD | 4.7 | 5.9 | 0.0041 | 2026-05-26 |
CVE-2026-112266 | 4.7 | 5.9 | 0.0042 | 2026-10-19 |
CVE-2026-14687 UPD | 4.5 | 5.3 | 0.0053 | 2026-07-05 |
CVE-2026-45692 UPD | 4.3 | 5.4 | 0.0024 | 2026-06-23 |
CVE-2026-81479 UPD | 4.3 | 5.8 | 0.0017 | 2026-09-17 |
CVE-2026-125371 | 3.9 | 4.8 | 0.0028 | 2026-11-10 |
CVE-2025-23384 UPD | 3.2 | 3.7 | 0.0028 | 2025-03-11 |