CVE-2019-16109: An issue was discovered in Plataformatec Devise before 4.7.1

Q: How do I fix CVE-2019-16109?

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

Q: Is CVE-2019-16109 being exploited?

CVE-2019-16109 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-2019-16109 affect?

CVE-2019-16109 affects devise. Severity is medium (CVSS 5.3). An issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value in the confirmation_token column. (However, there is no scen

Q: How urgent is CVE-2019-16109?

Priority 43/100. Remotely exploitable, no login, no user action

This month

MEDIUM 5.3REMOTEUPGRADE

CVE-2019-16109 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.

An issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value in the confirmation_token column. (However, there is no scenario within Devise itself in which such database records would exist.)

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 21%)
CISA exploited list	No
Published	2019-09-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: plataformatec

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

Am I affected?

Timeline

2019-09-08 20:15 UTCPublished CVE record published
2026-06-17 02:21 UTCUpdated Record last modified

plataformatec devise UPGRADE

Affected: < 4.7.1

Fixed in: 4.7.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 4.7.1 (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-2019-16109?

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

Is CVE-2019-16109 being exploited?

CVE-2019-16109 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-2019-16109 affect?

CVE-2019-16109 affects devise. Severity is medium (CVSS 5.3). An issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value in the confirmation_token column. (However, there is no scen

How urgent is CVE-2019-16109?

Priority 43/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-40295 MEDIUM 6.1 UPGRADE Devise is an authentication solution for Rails based on Warden
CVE-2026-32700 MEDIUM 5.3 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-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