VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

omniauth: vulnerability history, versions and safety

omniauth is a package in the RubyGems ecosystem. Vulert records 3 vulnerabilities for it across 60 releases, from Jan 2018 to Aug 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all omniauth vulnerabilities

Vulert verdict on omniauth 2.3.1 i

Updated on 23 Oct 2026

Good news: 2.3.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 90/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

What to do: Stay on 2.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.3.1 — unaffected i
  • Vulnerabilities on record 3 over 4 years · 0 in the last year i
  • Latest disclosure 19 Aug 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for omniauth, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.3.1 22 Oct 2026 none MIT — Details →
2.3.0 22 Oct 2026 none MIT — Details →
2.2.0 22 Oct 2026 none MIT — Details →
2.1.4 01 Oct 2025 none MIT — Details →
2.1.3 27 Feb 2025 none MIT — Details →
2.1.2 19 Dec 2023 none MIT — Details →
2.1.1 20 Jan 2023 none MIT — Details →
1.9.2 18 Aug 2022 H1 MIT Yes Details →
2.1.0 13 Apr 2022 none MIT — Details →
2.0.4 07 Apr 2021 none MIT — Details →
2.0.3 18 Feb 2021 none MIT — Details →
2.0.2 02 Feb 2021 none MIT — Details →
2.0.1 16 Jan 2021 none MIT — Details →
2.0.0 11 Jan 2021 none MIT — Details →
2.0.0.pre.rc1 11 Dec 2020 H1 MIT Yes Details →
1.9.1 02 Mar 2020 C1 H1 MIT Yes Details →
1.9.0 14 Dec 2018 C1 H1 MIT Yes Details →
1.8.1 28 Dec 2017 C1 H1 MIT Yes Details →
1.8.0 27 Dec 2017 C1 H1 MIT Yes Details →
1.4.3 18 Dec 2017 C1 H1 MIT Yes Details →
1.7.1 02 Oct 2017 C1 H1 MIT Yes Details →
1.7.0 28 Sep 2017 C1 H1 MIT Yes Details →
1.6.1 18 Feb 2017 C1 H1 MIT Yes Details →
1.6.0 17 Feb 2017 C1 H1 MIT Yes Details →
1.5.0 11 Feb 2017 C1 H1 MIT Yes Details →
1.4.2 11 Feb 2017 C1 H1 MIT Yes Details →
1.4.1 08 Feb 2017 C1 H1 MIT Yes Details →
1.4.0 06 Feb 2017 C1 H1 MIT Yes Details →
1.3.2 17 Jan 2017 C1 H1 MIT Yes Details →
1.3.1 20 Dec 2015 C1 H2 MIT Yes Details →
1.3.0 20 Dec 2015 C1 H2 MIT Yes Details →
1.2.2 09 Jul 2014 C1 H2 MIT Yes Details →
1.2.1 16 Jan 2014 C1 H2 MIT Yes Details →
1.1.4 08 Apr 2013 C1 H2 MIT Yes Details →
1.1.3 14 Feb 2013 C1 H2 MIT Yes Details →
1.1.2 08 Feb 2013 C1 H2 MIT Yes Details →
1.1.1 24 Aug 2012 C1 H2 — Yes Details →
1.1.0 13 Apr 2012 C1 H2 — Yes Details →
1.0.3 06 Mar 2012 C1 H2 — Yes Details →
1.0.2 17 Jan 2012 C1 H2 — Yes Details →
1.0.1 25 Nov 2011 C1 H2 — Yes Details →
1.0.0 02 Nov 2011 C1 H2 — Yes Details →
1.0.0.rc2 28 Oct 2011 C1 H2 — Yes Details →
1.0.0.rc1 28 Oct 2011 C1 H2 — Yes Details →
0.3.2 20 Oct 2011 C1 H2 — Yes Details →
1.0.0.beta1 19 Oct 2011 C1 H2 — Yes Details →
1.0.0.pr2 13 Oct 2011 C1 H2 — Yes Details →
1.0.0.pr1 13 Oct 2011 C1 H2 — Yes Details →
0.3.0 22 Sep 2011 C1 H2 — Yes Details →
0.3.0.rc3 03 Sep 2011 C1 H2 — Yes Details →
0.2.6 20 May 2011 C1 H2 — Yes Details →
0.2.5 29 Apr 2011 C1 H2 — Yes Details →
0.2.4 22 Apr 2011 C1 H2 — Yes Details →
0.2.3 21 Apr 2011 C1 H2 — Yes Details →
0.2.2 16 Apr 2011 C1 H2 — Yes Details →
0.2.1 05 Apr 2011 C1 H2 — Yes Details →
0.2.0 11 Mar 2011 C1 H2 — Yes Details →
0.2.0.beta5 01 Mar 2011 C1 H2 — Yes Details →
0.2.0.beta4 11 Feb 2011 C1 H2 — Yes Details →
0.2.0.beta3 04 Feb 2011 C1 H2 — Yes Details →
0.2.0.beta2 14 Jan 2011 C1 H2 — Yes Details →
0.2.0.beta1 29 Nov 2010 C1 H2 — Yes Details →
0.1.6 25 Oct 2010 C1 H2 — Yes Details →
0.1.5 19 Oct 2010 C1 H2 — Yes Details →
0.1.4 12 Oct 2010 C1 H2 — Yes Details →
0.1.3 11 Oct 2010 C1 H2 — Yes Details →
0.1.2 06 Oct 2010 C1 H2 — Yes Details →
0.1.1 04 Oct 2010 C1 H2 — Yes Details →
0.1.0 01 Oct 2010 C1 H2 — Yes Details →
0.0.5 01 Sep 2010 C1 H2 — Yes Details →
0.0.4 16 Aug 2010 C1 H2 — Yes Details →
0.0.3 01 May 2010 C1 H2 — Yes Details →
0.0.1 29 Apr 2010 C1 H2 — Yes Details →

All 73 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2019 1
  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for omniauth

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-36599: OmniAuth RubyGems - Unescaped message_key value in lib/omniauth/failure_endpoint.rb 9.8 critical 1.9.2 19 Aug 2022
CVE-2015-9284: Cross-site Request Forgery in OmniAuth 8.8 high 2.0.0 29 May 2019
CVE-2017-18076: Vulnerability in omniauth 7.5 high 1.3.2 29 Jan 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About omniauth

Is omniauth safe to use?

Vulert records 3 vulnerabilities for omniauth in RubyGems: 1 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is omniauth's Vulert package health score?

Vulert scores omniauth 90/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of omniauth affected?

No. 2.3.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does omniauth have?

3 vulnerabilities are recorded for omniauth in the RubyGems ecosystem: 1 critical, 2 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new omniauth vulnerabilities disclosed?

0 vulnerabilities were recorded for omniauth in the last 12 months, and the oldest entry in this database dates to 29 Jan 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of omniauth are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor omniauth for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the omniauth version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.