CWE-1467
Weakness AllowedUse of Singular Authentication Artifact for Multiple User Sessions
Abstraction: Base · Status: Incomplete
The product provides an authentication artifact, such as an authentication token, for an authenticated user session, but the same artifact is used for every authenticated user session, potentially across multiple different applications.
Mapping guidance
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
Notes
Maintenance · CWE 5.0 · 2026-10-28
This entry was created in CWE 5.0 to address known gaps in CWE coverage. It is not as complete as other new entries that were published in recent years. The CWE Team plans to work with the CWE community to make this entry more complete in later 5.x releases.
Content history
Suggested content for the use of an unbound, reusable authentication artifact, which directly resulted in this CWE entry. Much of the content provided in the contributor's submission was used directly for this CWE entry
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
Mitigation
Enforce re-authentication per user device. This prevents another user from obtaining the singular authentication artifact and making authenticated requests without authenticating.
Mitigation
Use unique authentication artifacts per user device that will only be accepted if used on that device.
Mitigation
Ensure that unique authentication artifacts are used for each application or service within an organization to prevent potential reuse across applications.
No CAPEC attack patterns related to this CWE.