CWE-694Use of Multiple Resources with Duplicate Identifier

Abstraction: Base · CVEs in our corpus: 14

The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.

If the product assumes that each resource has a unique identifier, the product could operate on the wrong resource if attackers can cause multiple resources to be associated with the same identifier.

Last updated: 14 October 2026 20:41 UTC

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent

Stop it (NIST 800-53 / CSF Protect)

ID.AM-02
PR.AA-01
ID.AM-08
IA-4 Identifier Management

Detect

Catch it (CSF Detect / Respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V8.4.1
V3.5.4
V6.8.1
V9.2.4

NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted

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.

Top CVEs of this weakness type, ranked by Risk Priority

CVE	Risk	CVSS	EPSS	Published
`CVE-2026-71327`	6.1	8.1	0.0048	2026-08-06
`CVE-2025-59048`	6.0	8.1	0.0027	2025-10-23
`CVE-2025-13609`	5.9	8.2	0.0044	2025-11-24
`CVE-2026-102634`	5.9	7.5	0.0058	2026-09-29
`CVE-2023-20100`	5.2	6.8	0.0077	2023-03-23
`CVE-2026-57024`	4.4	5.3	0.0042	2026-07-09
`CVE-2026-78359`	4.2	5.4	0.0016	2026-10-12
`CVE-2021-3436`	3.9	4.3	0.0098	2021-10-05
`CVE-2024-41146`	3.7	4.6	0.0032	2024-12-12
`CVE-2026-108752`	3.4	4.2	0.0024	2026-10-11
`CVE-2020-15187`	3.0	3.0	0.0152	2020-09-17
`CVE-2022-23721`	3.0	3.8	0.0022	2023-04-25
`CVE-2020-15185`	2.4	2.2	0.0088	2020-09-17