VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

pg: vulnerability history, versions and safety

pg is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems ecosystem.

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 pg vulnerabilities

Vulert verdict on pg 1.7.0 i

Updated on 23 Oct 2026

Good news: 1.7.0, the version you would install today, has no known vulnerabilities.

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1.7.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 870 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence BSD-2-Clause 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 pg, 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
1.7.0 02 Oct 2026 none BSD-2-Clause — Details →
1.6.3 29 Dec 2025 none BSD-2-Clause — Details →
1.6.2 02 Sep 2025 none BSD-2-Clause — Details →
1.6.1 03 Aug 2025 none BSD-2-Clause — Details →
1.6.0 27 Jul 2025 none BSD-2-Clause — Details →
1.6.0.rc2 16 Jul 2025 none BSD-2-Clause — Details →
1.6.0.rc1 28 Nov 2024 none BSD-2-Clause — Details →
1.5.9 24 Oct 2024 none BSD-2-Clause — Details →
1.5.8 06 Sep 2024 none BSD-2-Clause — Details →
1.5.7 28 Jul 2024 none BSD-2-Clause — Details →
1.5.6 01 Mar 2024 none BSD-2-Clause — Details →
1.5.5 15 Feb 2024 none BSD-2-Clause — Details →
1.5.4 01 Sep 2023 none BSD-2-Clause — Details →
1.5.3 28 Apr 2023 none BSD-2-Clause — Details →
1.5.2 26 Apr 2023 none BSD-2-Clause — Details →
1.5.1 24 Apr 2023 none BSD-2-Clause — Details →
1.5.0 24 Apr 2023 none BSD-2-Clause — Details →
1.4.6 26 Feb 2023 none BSD-2-Clause — Details →
1.4.5 17 Nov 2022 none BSD-2-Clause — Details →
1.4.4 11 Oct 2022 none BSD-2-Clause — Details →
1.4.3 09 Aug 2022 none BSD-2-Clause — Details →
1.4.2 27 Jul 2022 none BSD-2-Clause — Details →
1.4.1 24 Jun 2022 none BSD-2-Clause — Details →
1.4.0 20 Jun 2022 none BSD-2-Clause — Details →
1.3.5 31 Mar 2022 none BSD-2-Clause — Details →
1.3.4 10 Mar 2022 none BSD-2-Clause — Details →
1.3.3 22 Feb 2022 none BSD-2-Clause — Details →
1.3.2 14 Feb 2022 none BSD-2-Clause — Details →
1.3.1 01 Feb 2022 none BSD-2-Clause — Details →
1.3.0 23 Jan 2022 none BSD-2-Clause — Details →
1.3.0.rc4 22 Jan 2022 none BSD-2-Clause — Details →
1.3.0.rc3 13 Jan 2022 none BSD-2-Clause — Details →
1.3.0.rc2 08 Jan 2022 none BSD-2-Clause — Details →
1.3.0.rc1 27 Dec 2021 none BSD-2-Clause — Details →
1.2.3 18 Mar 2020 none BSD-2-Clause — Details →
1.2.2 08 Jan 2020 none BSD-2-Clause — Details →
1.2.1 02 Jan 2020 none BSD-2-Clause — Details →
1.2.0 24 Dec 2019 none BSD-2-Clause — Details →
1.1.4 09 Jan 2019 none BSD-3-Clause — Details →
1.1.3 07 Sep 2018 none BSD-3-Clause — Details →
1.1.2 29 Aug 2018 none BSD-3-Clause — Details →
1.1.1 27 Aug 2018 none BSD-3-Clause — Details →
1.1.0 24 Aug 2018 none BSD-3-Clause — Details →
1.1.0.pre20180730171000 30 Jul 2018 none BSD-3-Clause — Details →
1.1.0.pre20180730144600 30 Jul 2018 none BSD-3-Clause — Details →
1.0.0 10 Jan 2018 none BSD-3-Clause — Details →
0.21.0 12 Jun 2017 none BSD-3-Clause — Details →
0.20.0 10 Mar 2017 none BSD-3-Clause — Details →
0.19.1.pre20170124220800 25 Jan 2017 none BSD-3-Clause — Details →
0.19.1.pre20170115074000 15 Jan 2017 none BSD-3-Clause — Details →
0.19.0.pre20170115074000 15 Jan 2017 none BSD-3-Clause — Details →
0.19.0 22 Sep 2016 none BSD-3-Clause — Details →
0.19.0.pre20160904200247 04 Sep 2016 none BSD-3-Clause — Details →
0.19.0.pre20160820113039 20 Aug 2016 none BSD-3-Clause — Details →
0.19.0.pre20160817083826 17 Aug 2016 none BSD-3-Clause — Details →
0.19.0.pre20160810143640 10 Aug 2016 none BSD-3-Clause — Details →
0.19.0.pre20160409114042 09 Apr 2016 none BSD-3-Clause — Details →
0.18.4 13 Nov 2015 none non-standard — Details →
0.18.3 03 Sep 2015 none non-standard — Details →
0.18.2 14 May 2015 none non-standard — Details →
0.18.1 05 Jan 2015 none non-standard — Details →
0.18.0 03 Jan 2015 none non-standard — Details →
0.18.0.pre20141117110243 17 Nov 2014 none non-standard — Details →
0.18.0.pre20141017160319 17 Oct 2014 none non-standard — Details →
0.18.0.pre20141017155815 17 Oct 2014 none non-standard — Details →
0.18.0.pre20140820094244 20 Aug 2014 none non-standard — Details →
0.17.2.pre.546 25 Jul 2014 none non-standard — Details →
0.17.1 19 Dec 2013 none non-standard — Details →
0.17.0 16 Sep 2013 none non-standard — Details →
0.16.0 23 Jul 2013 none non-standard — Details →
0.15.1 08 Apr 2013 none non-standard — Details →
0.15.0 26 Mar 2013 none non-standard — Details →
0.15.0.pre.454 15 Mar 2013 none non-standard — Details →
0.15.0.pre.432 03 Feb 2013 none non-standard — Details →
0.14.1 02 Sep 2012 none — — Details →
0.14.1.pre.363 13 Aug 2012 none — — Details →
0.14.0 23 Jun 2012 none — — Details →
0.14.0.pre.353 17 Jun 2012 none — — Details →
0.14.0.pre.351 17 Jun 2012 none — — Details →
0.13.2 22 Feb 2012 none — — Details →
0.13.1 12 Feb 2012 none — — Details →
0.13.0 09 Feb 2012 none — — Details →
0.13.0.pre305 28 Jan 2012 none — — Details →
0.13.0.pre300 27 Jan 2012 none — — Details →
0.13.0.pre298 25 Jan 2012 none — — Details →
0.12.2 03 Jan 2012 none — — Details →
0.12.1 02 Jan 2012 none — — Details →
0.12.0 08 Dec 2011 none — — Details →
0.12.0.pre263 05 Dec 2011 none — — Details →
0.12.0pre258 07 Oct 2011 none — — Details →
0.11.0 19 Apr 2011 none — — Details →
0.11.0pre229 31 Mar 2011 none — — Details →
0.11.0pre220 23 Feb 2011 none — — Details →
0.10.1 19 Jan 2011 none — — Details →
0.10.1pre209 22 Dec 2010 none — — Details →
0.10.0 01 Dec 2010 none — — Details →
0.9.0 28 Feb 2010 none — — Details →
0.9.0.pre158 19 Feb 2010 none — — Details →
0.9.0.pre156 19 Feb 2010 none — — Details →
0.7.9.2008.01.28 25 Jul 2009 none — — Details →
0.7.9.2008.02.05 25 Jul 2009 none — — Details →
0.7.9.2008.03.18 25 Jul 2009 none — — Details →
0.7.9.2008.08.17 25 Jul 2009 none — — Details →
0.7.9.2008.10.05 25 Jul 2009 none — — Details →
0.7.9.2008.10.13 25 Jul 2009 none — — Details →
0.8.0 25 Jul 2009 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for pg

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 pg

Is pg safe to use?

Vulert has no vulnerabilities on record for pg in RubyGems at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is pg's Vulert package health score?

Vulert scores pg 82/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 pg affected?

No. 1.7.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 pg should I use?

1.7.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 pg have?

0 vulnerabilities are recorded for pg in the RubyGems ecosystem: 0 critical, 0 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 pg vulnerabilities disclosed?

0 vulnerabilities were recorded for pg in the last 12 months. 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 pg 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 pg for upcoming vulnerabilities?

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