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

> Attackers can confirm email addresses they do not own via a race condition in Devise's Confirmable module, potentially taking over accounts.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** DEBIAN-CVE-2026-32700, GHSA-57hq-95w6-v4fc, UBUNTU-CVE-2026-32700

## What is CVE-2026-32700?

CVE-2026-32700 is a medium-severity vulnerability in heartcombo devise, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 `confirmation_token` and `unconfirmed_email` fields. The confirmation token is sent to an email the attacker controls, but the `unconfirmed_email` 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 `unconfirmed_email` to be persisted when unchanged. Note that Mongoid does not seem to respect that `will_change!` 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 `changed_attributes["unconfirmed_email"] = nil` as well.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-32700?

2 open source packages ship an affected version, including devise. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `devise` | RubyGems | All versions | 5.0.3 |
| `devise` | RubyGems | All versions | 5.0.3 |

Products: Heartcombo Devise.

## How do I fix CVE-2026-32700?

Upgrade devise to 5.0.3 or later.

## Is CVE-2026-32700 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32700 exists.

## Other vulnerabilities in heartcombo devise

- [CVE-2015-8314](https://insights.sbomify.com/CVE-2015-8314/): Devise Gem for Ruby Unauthorized Access Using "Remember Me" Cookie (high 7.5)
- [CVE-2026-40295](https://insights.sbomify.com/CVE-2026-40295/): Devise: Open Redirect via Unvalidated `request.referrer` in Timeoutable Session Timeout Handler (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32700 and fix it if it is affected.

What it is: CVE-2026-32700 is a medium-severity vulnerability in heartcombo devise, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32700 exists.

Affected packages and fixed versions:
- devise (RubyGems): affected all versions; fixed in 5.0.3
- devise (RubyGems): affected all versions; fixed in 5.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32700/ (Markdown: https://insights.sbomify.com/CVE-2026-32700/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32700
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32700
- OSV: https://osv.dev/vulnerability/CVE-2026-32700

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32700/
Summaries are generated and may contain mistakes; the official description above is the record.