VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

omniauth-facebook: vulnerability history, versions and safety

omniauth-facebook is a package in the RubyGems ecosystem. Vulert records 2 vulnerabilities for it across 9 releases, from Oct 2017 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
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-facebook vulnerabilities

Vulert verdict on omniauth-facebook 11.0.0 i

Updated on 23 Oct 2026

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

Package health score 94/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 11.0.0 — unaffected i
  • Vulnerabilities on record 2 over 4 years · 0 in the last year i
  • Latest disclosure 05 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Last release 3 months ago 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-facebook, 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
11.0.0 18 Jul 2026 none MIT — Details →
10.0.0 22 May 2024 none MIT — Details →
9.0.0 25 Oct 2021 none MIT — Details →
8.0.0 19 Oct 2020 none MIT — Details →
7.0.0 26 Aug 2020 none MIT — Details →
6.0.0 27 Jan 2020 none MIT — Details →
5.0.0 10 Apr 2018 none MIT — Details →
4.0.0 27 Jul 2016 none MIT — Details →
4.0.0.rc1 27 Jun 2016 none MIT — Details →
3.0.0 27 Oct 2015 none MIT — Details →
2.0.1 21 Feb 2015 none MIT — Details →
2.0.0 07 Aug 2014 none MIT — Details →
2.0.0.pre1 12 May 2014 none MIT — Details →
1.6.0 11 Jan 2014 none MIT — Details →
1.6.0.rc1 03 Dec 2013 none MIT — Details →
1.5.1 18 Nov 2013 none — — Details →
1.5.0 13 Nov 2013 H1 — Yes Details →
1.4.1 07 Jul 2012 H1 M1 — Yes Details →
1.4.0 24 Jun 2012 H1 — Yes Details →
1.3.0 05 May 2012 H1 — Yes Details →
1.2.0 06 Jan 2012 H1 — Yes Details →
1.1.0 10 Dec 2011 H1 — Yes Details →
1.0.0 19 Nov 2011 H1 — Yes Details →
1.0.0.rc2 11 Nov 2011 H1 — Yes Details →
1.0.0.rc1 29 Oct 2011 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for omniauth-facebook

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2013-4593: omniauth-facebook Improper Authentication vulnerability 7.5 high 1.5.1 05 May 2022
CVE-2013-4562: omniauth-facebook Cross-Site Request Forgery vulnerability N/A medium 1.5.0 24 Oct 2017

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-facebook

Is omniauth-facebook safe to use?

Vulert records 2 vulnerabilities for omniauth-facebook in RubyGems: 0 critical, 1 high, 1 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-facebook's Vulert package health score?

Vulert scores omniauth-facebook 94/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-facebook affected?

No. 11.0.0, 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.

Which version of omniauth-facebook should I use?

11.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does omniauth-facebook have?

2 vulnerabilities are recorded for omniauth-facebook in the RubyGems ecosystem: 0 critical, 1 high, 1 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-facebook vulnerabilities disclosed?

0 vulnerabilities were recorded for omniauth-facebook in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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-facebook 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-facebook for upcoming vulnerabilities?

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