CVE-2020-26254

HIGHNVD 7.77.7
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: nvd
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.7Exploit: NoneExposed: 0

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

omniauth-apple is the OmniAuth strategy for "Sign In with Apple" (RubyGem omniauth-apple). In omniauth-apple before version 1.0.1 attackers can fake their email address during authentication. This vulnerability impacts applications using the omniauth-apple strategy of OmniAuth and using the info.email field of OmniAuth's Auth Hash Schema for any kind of identification. The value of this field may be set to any value of the attacker's choice including email addresses of other users. Applications not using info.email for identification but are instead using the uid field are not impacted in the same manner. Note, these applications may still be negatively affected if the value of info.email is being used for other purposes. Applications using affected versions of omniauth-apple are advised to upgrade to omniauth-apple version 1.0.1 or later.

CVSS v3
7.7
EG Score
7.7(low)
EPSS
67.9%
KEV
Not listed

Published

December 8, 2020

Last Modified

November 21, 2024

References (6)

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
omniauth-apple0.0.1, 0.0.2, 0.0.3, 1.0.01.0.1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2020-26254?
CVE-2020-26254 is a high vulnerability published on December 8, 2020. omniauth-apple is the OmniAuth strategy for "Sign In with Apple" (RubyGem omniauth-apple). In omniauth-apple before version 1.0.1 attackers can fake their email address during authentication. This vulnerability impacts applications using the omniauth-apple strategy of OmniAuth and using the…
When was CVE-2020-26254 disclosed?
CVE-2020-26254 was first published in the National Vulnerability Database on December 8, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-26254 actively exploited?
CVE-2020-26254 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 67.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-26254?
CVE-2020-26254 has a CVSS v3 base score of 7.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2020-26254?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-26254, 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-2020-26254

Explore →

Is Your Infrastructure Affected by CVE-2020-26254?

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

Start Free Scan →Browse All CVEs