CVE-2026-32700: Devise has a confirmable "change email" race condition that permits user to confirm email they have no access to

Published Mar 17, 2026
·
Updated

Impact

A race condition in Devise's Confirmable module allows an attacker to confirm an email address they do not own. This affects any Devise application using the reconfirmable option (the default when using Confirmable with email changes).

By sending two concurrent email change requests, an attacker can desynchronize the confirmationtoken and unconfirmedemail fields. The confirmation token is sent to an email the attacker controls, but the unconfirmedemail in the database points to a victim's email address. When the attacker uses the token, the victim's email is confirmed on the attacker's account.

Patches

This is patched in Devise v5.0.3. Users should upgrade as soon as possible.

Workarounds

Applications can override this specific method from Devise models to force unconfirmedemail to be persisted when unchanged: (assuming your model is User)

ruby class User < ApplicationRecord protected

def postponeemailchangeuntilconfirmationandregenerateconfirmationtoken unconfirmedemailwillchange! super end end

Note: Mongoid does not seem to respect that willchange! should force the attribute to be persisted, even if it did not really change, so you might have to implement a workaround similar to Devise by setting changedattributes["unconfirmedemail"] = nil as well.

Other sources

Devise is an authentication solution for Rails based on Warden. Prior to version 5.0.3, a race condition in Devise's Confirmable module allows an attacker to confirm an email address they do not own. This affects any Devise application using the reconfirmable option (the default when using Confirmable with email changes). By sending two concurrent email change requests, an attacker can desynchronize the confirmationtoken and unconfirmedemail fields. The confirmation token is sent to an email the attacker controls, but the unconfirmedemail in the database points to a victim's email address. When the attacker uses the token, the victim's email is confirmed on the attacker's account. This is patched in Devise v5.0.3. Users should upgrade as soon as possible. As a workaround, applications can override a specific method from Devise models to force unconfirmedemail to be persisted when unchanged. Note that Mongoid does not seem to respect that willchange! should force the attribute to be persisted, even if it did not really change, so the user might have to implement a workaround similar to Devise by setting changedattributes["unconfirmedemail"] = nil as well.

MITRE

Affected Software

2 affected componentsFixes available
rubygems/devise<=5.0.2
5.0.3
Heartcombo Devise Ruby<5.0.3

Event History

Mar 17, 2026
Advisory Published
via GitHub·05:24 PM
Data Sourced
via GitHub·05:24 PM
DescriptionWeaknessAffected Software
Mar 18, 2026
CVE Published
via MITRE·08:55 PM
Data Sourced
via MITRE·08:55 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
RemedyAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-32700?

The severity of CVE-2026-32700 is considered high due to its ability to allow an attacker to confirm an email address they do not own.

2

How do I fix CVE-2026-32700?

To fix CVE-2026-32700, upgrade the Devise gem to version 5.0.3 or later.

3

What causes the vulnerability in CVE-2026-32700?

CVE-2026-32700 is caused by a race condition in the Confirmable module of Devise that affects email confirmation.

4

Who is affected by CVE-2026-32700?

Any application using versions of the Devise gem prior to 5.0.3 with the `reconfirmable` option enabled is affected by CVE-2026-32700.

5

What is the impact of exploiting CVE-2026-32700?

Exploiting CVE-2026-32700 allows an attacker to confirm an email address they do not control, potentially leading to unauthorized access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203