CVE-2024-21632

CRITICALNVD 9.88.6▼
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
8.6(medium)
EPSS
55.6%
KEV
Not listed

Published

January 2, 2024

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jun 27, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic🟡 PoC Available

nOAuth: How Microsoft OAuth Misconfiguration Can Lead to Full Account Takeover

https://www.descope.com/blog/post/noauth
github Patch Available

Account takeover (nOAuth) · Advisory · synth/omniauth-microsoft_graph · GitHub

https://github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-628f-7cvj
github_commit Patch Available

commit f13207838961 (synth/omniauth-microsoft_graph)

Patch available: synth/omniauth-microsoft_graph 2.0.0 (contains commit f13207838961)

https://github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b45bd0e0b47382414c1

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
omniauth-microsoft_graph0.1.0 ... 1.2.0 (11 versions)2.0.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-14 23:40 UTCOSV refresh
  2. 2026-07-13 22:28 UTCEPSS rescore
  3. 2026-07-13 06:11 UTCEPSS rescore
  4. 2026-07-13 06:11 UTCEPSS rescore
  5. 2026-07-12 05:45 UTCEPSS rescore
  6. 2026-07-11 08:26 UTCEPSS rescore
  7. 2026-07-09 19:09 UTCEPSS rescore
  8. 2026-07-09 19:09 UTCEPSS rescore
  9. 2026-07-08 15:13 UTCEPSS rescore
  10. 2026-07-07 13:45 UTCEPSS rescore
  11. 2026-07-07 13:45 UTCEPSS rescore
  12. 2026-07-06 16:26 UTCEPSS rescore
  13. 2026-07-06 02:22 UTCEPSS rescore
  14. 2026-07-06 02:22 UTCEPSS rescore
  15. 2026-07-05 02:29 UTCEPSS rescore
  16. 2026-07-04 06:30 UTCEPSS rescore
  17. 2026-07-01 15:05 UTCEPSS rescore
  18. 2026-06-30 23:21 UTCEPSS rescore
  19. 2026-06-30 23:21 UTCEPSS rescore
  20. 2026-06-29 14:05 UTCEPSS rescore
  21. 2026-06-28 14:06 UTCEPSS rescore
  22. 2026-06-28 14:06 UTCEPSS rescore
  23. 2026-06-28 04:55 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-27 03:07 UTCEPSS rescore
Show 68 more
  1. 2026-06-27 03:07 UTCEPSS rescore
  2. 2026-06-27 00:37 UTCOSV refresh
  3. 2026-06-25 13:48 UTCEPSS rescore
  4. 2026-06-25 13:48 UTCEPSS rescore
  5. 2026-06-24 14:04 UTCEPSS rescore
  6. 2026-06-24 14:04 UTCEPSS rescore
  7. 2026-06-24 06:36 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  8. 2026-06-23 21:32 UTCEPSS rescore
  9. 2026-06-23 21:32 UTCEPSS rescore
  10. 2026-06-22 14:24 UTCEPSS rescore
  11. 2026-06-22 14:24 UTCEPSS rescore
  12. 2026-06-21 14:55 UTCEPSS rescore
  13. 2026-06-21 14:55 UTCEPSS rescore
  14. 2026-06-21 01:58 UTCEPSS rescore
  15. 2026-06-21 01:58 UTCEPSS rescore
  16. 2026-06-19 19:24 UTCEPSS rescore
  17. 2026-06-19 19:24 UTCEPSS rescore
  18. 2026-06-18 17:51 UTCEPSS rescore
  19. 2026-06-18 17:51 UTCEPSS rescore
  20. 2026-06-17 17:52 UTCEPSS rescore
  21. 2026-06-17 17:52 UTCEPSS rescore
  22. 2026-06-16 17:51 UTCEPSS rescore
  23. 2026-06-16 17:51 UTCEPSS rescore
  24. 2026-06-15 17:47 UTCEPSS rescore
  25. 2026-06-14 23:16 UTCEPSS rescore
  26. 2026-06-13 22:59 UTCEPSS rescore
  27. 2026-06-13 22:59 UTCEPSS rescore
  28. 2026-06-12 23:11 UTCEPSS rescore
  29. 2026-06-11 13:59 UTCEPSS rescore
  30. 2026-06-11 13:59 UTCEPSS rescore
  31. 2026-06-10 22:17 UTCEPSS rescore
  32. 2026-06-10 13:21 UTCEPSS rescore
  33. 2026-06-10 13:21 UTCEPSS rescore
  34. 2026-06-09 10:56 UTCOSV refresh
  35. 2026-06-08 14:16 UTCEPSS rescore
  36. 2026-06-08 14:16 UTCEPSS rescore
  37. 2026-06-07 15:24 UTCEPSS rescore
  38. 2026-06-07 15:24 UTCEPSS rescore
  39. 2026-06-06 13:46 UTCEPSS rescore
  40. 2026-06-06 13:46 UTCEPSS rescore
  41. 2026-06-05 22:46 UTCEPSS rescore
  42. 2026-06-05 22:46 UTCEPSS rescore
  43. 2026-06-05 06:09 UTCEPSS rescore
  44. 2026-06-05 06:09 UTCEPSS rescore
  45. 2026-06-04 13:11 UTCEPSS rescore
  46. 2026-06-04 13:11 UTCEPSS rescore
  47. 2026-06-04 13:11 UTCEPSS rescore
  48. 2026-06-02 20:12 UTCEPSS rescore
  49. 2026-06-02 20:12 UTCEPSS rescore
  50. 2026-06-01 13:51 UTCEPSS rescore
  51. 2026-06-01 13:51 UTCEPSS rescore
  52. 2026-06-01 13:51 UTCEPSS rescore
  53. 2026-05-31 22:30 UTCEPSS rescore
  54. 2026-05-31 22:30 UTCEPSS rescore
  55. 2026-05-31 00:15 UTCEPSS rescore
  56. 2026-05-31 00:15 UTCEPSS rescore
  57. 2026-05-29 13:43 UTCEPSS rescore
  58. 2026-05-29 13:43 UTCEPSS rescore
  59. 2026-05-28 13:44 UTCEPSS rescore
  60. 2026-05-28 13:44 UTCEPSS rescore
  61. 2026-05-28 13:44 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-27 13:40 UTCEPSS rescore
  64. 2026-05-26 13:43 UTCEPSS rescore
  65. 2026-05-26 13:43 UTCEPSS rescore
  66. 2026-05-26 07:18 UTCEPSS rescore
  67. 2026-05-26 07:18 UTCEPSS rescore
  68. 2026-05-24 11:10 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-21632?
CVE-2024-21632 is a critical vulnerability published on January 2, 2024. 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 was CVE-2024-21632 disclosed?
CVE-2024-21632 was first published in the National Vulnerability Database on January 2, 2024, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-21632 actively exploited?
CVE-2024-21632 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 55.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-21632?
CVE-2024-21632 has a CVSS v3 base score of 9.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.6.
How do I remediate CVE-2024-21632?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-21632, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-21632

Explore →

Is Your Infrastructure Affected by CVE-2024-21632?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs