CVE-2026-104143

Requiring unique identification and authentication of users forces the system to resolve all name variants to a single identity before access is granted.

Identifier management directly requires authorization and uniqueness checks that eliminate alternate-name aliases for the same actor or resource.

Proper identity management reduces alternate-name collisions but does not guarantee canonicalization inside the auth decision.

Strong authentication mechanisms directly prevent name-based bypass when they enforce canonical name checks.

Authorization policy enforcement assumes correct identity; the weakness occurs before policy is applied.

A.5.15 only requires defining and documenting an access control policy plus requirements; it does not itself enforce rules or stop alternate-name authentication bypasses from being exploitable.

A.5.16 manages the lifecycle, uniqueness, and accountability of identities; it has no bearing on a product that authenticates by name but fails to canonicalize or check alternate names for the same resource/actor, so the weakness remains present and exploitable.

Proper management of authentication credentials can include rules against duplicate or alias identities.

A.5.18 governs the provisioning, review, and revocation of already-granted access rights to authenticated identities; it does not address or stop the distinct flaw in which authentication logic accepts an alternate name that bypasses the check.