CWE-694: Use of Multiple Resources with Duplicate Identifier

Base

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.

Consequences

Access Control: Bypass Protection Mechanism
Other: Quality Degradation

How to prevent it

Architecture and Design: Where possible, use unique identifiers. If non-unique identifiers are detected, then do not operate any resource with a non-unique identifier and report the error appropriately.

Recent advisories

GHSA-2g95-wg33-c5x2 — filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse
GO-2026-6209 — Traefik: Gateway API route identity collision allows cross-namespace backend hijacking
GHSA-c52f-pq47-2r9j — plugin.yaml file allows for duplicate entries in helm
GHSA-jm56-5h66-w453 — Repository index file allows for duplicates of the same chart entry in helm

All advisories for CWE-694

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor