Unverified50% confidenceFactExact time
An email enumeration attack is when an attacker infers which email addresses are already registered in a system by observing differences in the system's responses to different email addresses (such as response time, error messages, whether an email is sent, etc.).
1
Sources
50%
Confidence
Long-term
Relevance
11/4/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIf the identity provider has not verified the email, an attacker can change the email to the target user's address, and at login it will be linked to the existing account, leading to account takeover.74% similarUnverifiedThe core principle for defending against email enumeration attacks is response consistency: regardless of whether the email exists, the API should return the same status code, the same message text, and roughly the same response time, and should also execute equivalent placeholder logic for non-existent emails.73% similarUnverifiedThe exposure of username-to-email address mappings can be used for cross-platform credential stuffing attacks, particularly against users who reuse the same password.73% similarUnverifiedThe email scenario is a typical case of indirect prompt injection: the attacker does not need to contact the victim and can complete the poisoning simply by sending one email.73% similarUnverifiedTo prevent email enumeration attacks, in the Magic Auth flow the same response should be returned regardless of whether the email exists, but emails are sent only to addresses that do exist.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1135004API
curl https://kongchang.com/api/v1/knowledge/claims/1135004MCP
get_claim(id=1135004)