VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

passenger: vulnerability history, versions and safety

passenger is a package in the RubyGems ecosystem. Vulert records 14 vulnerabilities for it across 80 releases, from Oct 2017 to Feb 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded C1 H5 M5 L3
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 passenger vulnerabilities

Vulert verdict on passenger 6.2.1 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 6.2.1 — unaffected i
  • Vulnerabilities on record 14 over 7 years · 0 in the last year i
  • Latest disclosure 24 Feb 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 5,092 i
  • OpenSSF scorecard 4/10 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 passenger, 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
6.2.1 19 Oct 2026 none — — Details →
6.2.0 18 Aug 2026 none — — Details →
6.1.8 20 Jul 2026 none — — Details →
6.1.7 06 Jul 2026 none — — Details →
6.1.6 27 Jun 2026 none — — Details →
6.1.5 09 Jun 2026 none — — Details →
6.1.4 02 Jun 2026 none — — Details →
6.1.3 19 May 2026 none — — Details →
6.1.2 30 Jan 2026 none — — Details →
6.1.1 23 Dec 2025 none — — Details →
6.1.0 17 Sep 2025 none — — Details →
6.0.27 04 Apr 2025 none — — Details →
6.0.26 19 Feb 2025 none — — Details →
6.0.25 12 Feb 2025 M1 — Yes Details →
6.0.24 09 Dec 2024 M1 — Yes Details →
6.0.23 29 Jul 2024 M1 — Yes Details →
6.0.22 18 May 2024 M1 — Yes Details →
6.0.21 17 May 2024 M1 — Yes Details →
6.0.20 22 Jan 2024 none — — Details →
6.0.19 20 Nov 2023 none — — Details →
6.0.18 12 Jun 2023 none — — Details →
6.0.17 25 Jan 2023 none — — Details →
6.0.16 19 Dec 2022 none — — Details →
6.0.15 19 Sep 2022 none — — Details →
6.0.14 10 May 2022 none — — Details →
6.0.13 29 Mar 2022 none — — Details →
6.0.12 05 Nov 2021 none — — Details →
6.0.11 01 Oct 2021 none — — Details →
6.0.10 14 Jul 2021 none — — Details →
6.0.9 02 Jun 2021 none — — Details →
6.0.8 01 Apr 2021 none — — Details →
6.0.7 18 Nov 2020 none — — Details →
6.0.6 14 Jul 2020 none — — Details →
6.0.5 29 May 2020 none — — Details →
6.0.4 18 Sep 2019 none — — Details →
6.0.3 12 Sep 2019 none — — Details →
6.0.2 25 Feb 2019 none — — Details →
6.0.1 07 Jan 2019 none — — Details →
6.0.0 30 Nov 2018 none — — Details →
5.3.7 10 Nov 2018 none — — Details →
5.3.6 05 Nov 2018 none — — Details →
5.3.5 24 Sep 2018 none — — Details →
5.3.4 01 Aug 2018 none — — Details →
5.3.3 26 Jun 2018 none — — Details →
5.3.2 12 Jun 2018 none — — Details →
5.3.1 14 May 2018 C1 H3 M1 — Yes Details →
5.3.0 09 May 2018 C1 H3 M1 — Yes Details →
5.2.3 04 Apr 2018 H1 M1 — Yes Details →
5.2.2 28 Mar 2018 H1 M1 — Yes Details →
5.2.1 27 Feb 2018 H1 M1 — Yes Details →
5.2.0 29 Jan 2018 H1 M1 — Yes Details →
5.1.12 23 Nov 2017 H1 M1 — Yes Details →
5.1.11 16 Oct 2017 H1 M1 — Yes Details →
5.1.10 12 Oct 2017 H1 M2 — Yes Details →
5.1.9 12 Oct 2017 H1 M2 — Yes Details →
5.1.8 23 Aug 2017 H1 M2 — Yes Details →
5.1.7 01 Aug 2017 H1 M2 — Yes Details →
5.1.6 20 Jul 2017 H1 M2 — Yes Details →
5.1.5 16 Jun 2017 H1 M2 — Yes Details →
5.1.4 09 May 2017 H1 M2 — Yes Details →
5.1.3 02 May 2017 H1 M2 — Yes Details →
5.1.2 25 Jan 2017 H1 M2 — Yes Details →
5.1.1 22 Dec 2016 H1 M2 — Yes Details →
5.1.0 15 Dec 2016 H1 M2 — Yes Details →
5.0.30 25 Jul 2016 H2 M2 — Yes Details →
5.0.29 22 Jun 2016 H2 M2 — Yes Details →
5.0.28 28 Apr 2016 H2 M2 — Yes Details →
5.0.27 06 Apr 2016 H2 M2 — Yes Details →
5.0.26 01 Mar 2016 H2 M2 — Yes Details →
5.0.25 18 Feb 2016 H2 M2 — Yes Details →
5.0.24 01 Feb 2016 H2 M2 — Yes Details →
5.0.23 21 Dec 2015 H2 M2 — Yes Details →
5.0.22 07 Dec 2015 H2 M2 — Yes Details →
4.0.60 07 Dec 2015 H2 M2 — Yes Details →
5.0.21 22 Oct 2015 H2 M2 — Yes Details →
5.0.20 25 Sep 2015 H2 M2 — Yes Details →
5.0.19 24 Sep 2015 H2 M2 — Yes Details →
5.0.18 09 Sep 2015 H2 M2 — Yes Details →
5.0.17 08 Sep 2015 H2 M2 — Yes Details →
5.0.16 24 Aug 2015 H2 M2 — Yes Details →
5.0.15 29 Jul 2015 H2 M2 — Yes Details →
5.0.14 15 Jul 2015 H2 M2 — Yes Details →
5.0.13 02 Jul 2015 H2 M2 — Yes Details →
5.0.11 23 Jun 2015 H2 M2 — Yes Details →
5.0.10 10 Jun 2015 H2 M2 — Yes Details →
5.0.9 03 Jun 2015 H2 M2 — Yes Details →
5.0.8 20 May 2015 H2 M2 — Yes Details →
5.0.7 28 Apr 2015 H2 M2 — Yes Details →
5.0.6 31 Mar 2015 H2 M2 — Yes Details →
5.0.5 24 Mar 2015 H2 M2 — Yes Details →
5.0.4 11 Mar 2015 H2 M2 — Yes Details →
5.0.3 11 Mar 2015 H2 M2 — Yes Details →
5.0.2 07 Mar 2015 H2 M2 — Yes Details →
5.0.1 04 Mar 2015 H2 M2 — Yes Details →
5.0.0.rc2 20 Feb 2015 H2 M2 — Yes Details →
5.0.0.rc1 19 Feb 2015 H2 M2 — Yes Details →
4.0.59 09 Feb 2015 H2 M2 L1 — Yes Details →
5.0.0.beta3 09 Feb 2015 H2 M2 — Yes Details →
4.0.58 22 Jan 2015 H2 M2 L1 — Yes Details →
4.0.57 03 Jan 2015 H2 M2 L1 — Yes Details →
5.0.0.beta2 19 Dec 2014 H2 M2 — Yes Details →
4.0.56 18 Dec 2014 H2 M2 L1 — Yes Details →
4.0.55 12 Dec 2014 H2 M2 L1 — Yes Details →
5.0.0.beta1 25 Nov 2014 H2 M2 — Yes Details →
4.0.53 01 Oct 2014 H2 M2 L1 — Yes Details →
4.0.52 24 Sep 2014 H2 M2 L1 — Yes Details →
4.0.51 24 Sep 2014 H2 M2 L1 — Yes Details →
4.0.50 27 Aug 2014 H2 M2 L1 — Yes Details →
4.0.49 22 Aug 2014 H2 M2 L1 — Yes Details →
4.0.48 24 Jul 2014 H2 M2 L1 — Yes Details →
4.0.46 14 Jul 2014 H2 M2 L1 — Yes Details →
4.0.45 12 Jun 2014 H2 M2 L1 — Yes Details →
4.0.44 29 May 2014 H2 M2 L1 — Yes Details →
4.0.43 28 May 2014 H2 M2 L1 — Yes Details →
4.0.42 07 May 2014 H2 M2 L1 — Yes Details →
4.0.41 08 Apr 2014 H2 M2 L1 — Yes Details →
4.0.40 18 Mar 2014 H2 M2 L1 — Yes Details →
4.0.39 18 Mar 2014 H2 M2 L1 — Yes Details →
4.0.38 10 Mar 2014 H2 M2 L1 — Yes Details →
4.0.37 28 Jan 2014 H2 M2 L3 — Yes Details →

The newest 120 of 208 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2018 4
  • 2022 7
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for passenger

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-12026: Phusion Passenger SpawningKit Contains Arbitrary Read/Write Vulnerability 9.8 critical 5.3.2 14 May 2022
CVE-2018-12027: Insecure Permissions in Phusion Passenger 8.8 high 5.3.2 13 May 2022
CVE-2018-12028: Incorrect Access Control in Phusion Passenger 7.8 high 5.3.2 13 May 2022
CVE-2016-10345: Phusion Passenger Known /tmp Filename Vulnerability 7.8 high 5.1.0 21 Aug 2018
CVE-2012-6135: RubyGems passenger gem allows remote attackers to delete files 7.5 high 4.0.0.rc4 23 Apr 2022

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 passenger

Is passenger safe to use?

Vulert records 14 vulnerabilities for passenger in RubyGems: 1 critical, 5 high, 5 medium and 3 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 passenger's Vulert package health score?

Vulert scores passenger 79/100, which reads as in good shape. 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 passenger affected?

No. 6.2.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 passenger have?

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

How often are new passenger vulnerabilities disclosed?

0 vulnerabilities were recorded for passenger 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 passenger 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 passenger for upcoming vulnerabilities?

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