CVE-2024-21632: omniauth-microsoft_graph provides an Omniauth strategy for the Microsoft Graph API

Q: How do I fix CVE-2024-21632?

omniauth\: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-21632 being exploited?

CVE-2024-21632 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-2024-21632 affect?

CVE-2024-21632 affects omniauth\. Severity is high (CVSS 8.6). omniauth-microsoft_graph provides an Omniauth strategy for the Microsoft Graph API. Prior to versions 2.0.0, the implementation did not validate the legitimacy of the `email` attribute of the user nor did it give/document an option to do so

Q: How urgent is CVE-2024-21632?

Priority 60/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

This week

HIGH 8.6REMOTEWATCHLISTUPGRADE

CVE-2024-21632 is a high-severity flaw (CVSS 8.6) affecting omniauth\. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

omniauth-microsoft_graph provides an Omniauth strategy for the Microsoft Graph API. Prior to versions 2.0.0, the implementation did not validate the legitimacy of the `email` attribute of the user nor did it give/document an option to do so, making it susceptible to nOAuth misconfiguration in cases when the `email` is used as a trusted user identifier. This could lead to account takeover. Version 2.0.0 contains a fix for this issue.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-287
Published	2024-01-02
Last modified	2026-06-17

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

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

Am I affected?

Timeline

2024-01-02 22:15 UTCPublished CVE record published
2026-06-17 07:09 UTCUpdated Record last modified

recognizeapp omniauth\ UPGRADE

Affected: < 2.0.0

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade omniauth

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-2024-21632?

omniauth\: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2024-21632 being exploited?

CVE-2024-21632 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-2024-21632 affect?

CVE-2024-21632 affects omniauth\. Severity is high (CVSS 8.6). omniauth-microsoft_graph provides an Omniauth strategy for the Microsoft Graph API. Prior to versions 2.0.0, the implementation did not validate the legitimacy of the `email` attribute of the user nor did it give/document an option to do so

How urgent is CVE-2024-21632?

Priority 60/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

References

← Back to latest CVEs