CVE-2026-32700: Devise is an authentication solution for Rails based on Warden

Q: How do I fix CVE-2026-32700?

devise: upgrade to 5.0.3. Exact commands for each OS are on this page.

Q: Is CVE-2026-32700 being exploited?

CVE-2026-32700 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-32700 affect?

CVE-2026-32700 affects devise. Severity is medium (CVSS 5.3). 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 usin

Q: How urgent is CVE-2026-32700?

Priority 24/100. No elevated risk signals yet.

Routine

MEDIUM 5.3UPGRADE

CVE-2026-32700 is a medium-severity flaw (CVSS 5.3) affecting devise. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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_ema

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-362
Published	2026-03-18
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: heartcombo

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-18 21:16 UTCPublished CVE record published
2026-06-17 10:36 UTCUpdated Record last modified

heartcombo devise UPGRADE

Affected: < 5.0.3

Fixed in: 5.0.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy devise || rpm -q devise || devise --version

2. UPGRADE to 5.0.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade devise

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade devise

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-32700?

devise: upgrade to 5.0.3. Exact commands for each OS are on this page.

Is CVE-2026-32700 being exploited?

CVE-2026-32700 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-32700 affect?

CVE-2026-32700 affects devise. Severity is medium (CVSS 5.3). 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 usin

How urgent is CVE-2026-32700?

Priority 24/100. No elevated risk signals yet.

Software pages

Ruby on Rails vulnerabilities

Related CVEs

CVE-2026-40295 MEDIUM 6.1 UPGRADE Devise is an authentication solution for Rails based on Warden
CVE-2019-5421 CRITICAL 9.8 UPGRADE Plataformatec Devise version 4.5.0 and earlier, using the lockable module contains a CWE-367 vulnerability in
CVE-2019-16109 MEDIUM 5.3 UPGRADE An issue was discovered in Plataformatec Devise before 4.7.1
CVE-2015-8314 HIGH 7.5 UPGRADE The Devise gem before 3.5.4 for Ruby mishandles Remember Me cookies for sessions, which may allow an adversary

References

← Back to latest CVEs