Skip to content

Password reset email path lacks cooldown allowing anonymous inbox flooding #55244

Description

@msdaly200

Describe the bug

The standalone password-reset flow (/realms/{realm}/login-actions/reset-credentials) has no application-level cooldown or per-user limit on reset emails. Each eligible request creates a new action token and sends a reset email. The verify-email and update-email flows use EmailCooldownManager to rate-limit emails, but ResetCredentialEmail does not.

An unauthenticated user who knows a valid username or email address can trigger repeated reset emails to that user's inbox. The impact is limited to inbox flooding for a targeted user and extra SMTP load. It does not lead to account compromise or data exposure.

Classification: weakness (hardening)

Version: Present in main

Expected behavior

Repeated reset-credentials requests for the same user within a short period should not each send an email. The response should stay the same generic response, so it doesn't reveal whether the account exists, but the email send should be suppressed. This is how the verify-email and update-email flows already behave.

Actual behavior

Every eligible reset-credentials request sends a new reset email, with no cooldown or limit.

Affected components

  • LoginActionsService: the /login-actions/reset-credentials endpoint, which creates a new authentication session for each anonymous request.
  • ResetCredentialChooseUser: selects the user from the submitted username or email.
  • ResetCredentialEmail: creates a new action token and sends the reset email on every eligible request, without checking EmailCooldownManager.
  • DefaultEmailSenderProvider: sends the email synchronously, so each accepted request uses real outbound mail work.

This issue was originally tracked in the private repository. Migrated by @msdaly200.

Activity

  1. added
    area/authenticationAuth flows, authenticators, required actions, OTP, password policies, brute force
    on Nov 16, 2026
  2. self-assigned this
    on Nov 17, 2026
  3. added 4 commits that reference this issue on Nov 18, 2026
    d33371d
    4eaea57
    dd67795
    d1ee405
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Fields

No fields configured for weakness.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions