VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pg: vulnerability history, versions and safety

pg is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Jul 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
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 8.23.1 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 8.23.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Jul 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 20,566 packages i
  • Stars 13,224 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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
8.23.1 30 Sep 2026 none MIT — Details →
8.23.0 08 Aug 2026 none MIT — Details →
8.22.0 19 Jun 2026 none MIT — Details →
8.21.0 18 May 2026 none MIT — Details →
8.20.0 04 Mar 2026 none MIT — Details →
8.19.0 25 Feb 2026 none MIT — Details →
8.18.0 30 Jan 2026 none MIT — Details →
8.17.2 20 Jan 2026 none MIT — Details →
8.17.1 15 Jan 2026 none MIT — Details →
8.17.0 14 Jan 2026 none MIT — Details →
8.16.3 27 Jun 2025 none MIT — Details →
8.16.2 19 Jun 2025 none MIT — Details →
8.16.1 18 Jun 2025 none MIT — Details →
8.16.0 12 May 2025 none MIT — Details →
8.15.6 25 Apr 2025 none MIT — Details →
8.15.5 23 Apr 2025 none MIT — Details →
8.15.2 23 Apr 2025 none MIT — Details →
8.15.1 22 Apr 2025 none MIT — Details →
8.15.0 22 Apr 2025 none MIT — Details →
8.14.2-alpha.1 21 Apr 2025 none MIT — Details →
8.14.2-alpha.0 21 Apr 2025 none MIT — Details →
8.14.1 17 Mar 2025 none MIT — Details →
8.14.0 11 Mar 2025 none MIT — Details →
8.13.3 13 Feb 2025 none MIT — Details →
8.13.2 11 Feb 2025 none MIT — Details →
8.13.1 24 Oct 2024 none MIT — Details →
8.13.0 17 Sep 2024 none MIT — Details →
8.12.0 04 Jun 2024 none MIT — Details →
8.11.6 04 Jun 2024 none MIT — Details →
8.11.5 02 Apr 2024 none MIT — Details →
8.11.4 30 Mar 2024 none MIT — Details →
8.11.3 16 Aug 2023 none MIT — Details →
8.11.2 01 Aug 2023 none MIT — Details →
8.11.1 26 Jun 2023 none MIT — Details →
8.11.0 15 May 2023 none MIT — Details →
8.10.0 06 Mar 2023 none MIT — Details →
8.9.0 27 Jan 2023 none MIT — Details →
8.8.0 23 Aug 2022 none MIT — Details →
8.7.3 04 Feb 2022 none MIT — Details →
8.7.1 27 Jul 2021 none MIT — Details →
8.7.0 27 Jul 2021 none MIT — Details →
8.6.0 13 Apr 2021 none MIT — Details →
8.5.1 13 Nov 2020 none MIT — Details →
8.5.0 10 Nov 2020 none MIT — Details →
8.4.2 26 Oct 2020 none MIT — Details →
8.4.1 08 Oct 2020 none MIT — Details →
8.4.0 04 Oct 2020 none MIT — Details →
8.3.3 26 Aug 2020 none MIT — Details →
8.3.2 18 Aug 2020 none MIT — Details →
8.3.0 09 Jul 2020 none MIT — Details →
8.2.2 07 Jul 2020 none MIT — Details →
8.2.1 15 May 2020 none MIT — Details →
8.2.0 13 May 2020 none MIT — Details →
8.1.0 08 May 2020 none MIT — Details →
8.0.3 22 Apr 2020 none MIT — Details →
8.0.2 09 Apr 2020 none MIT — Details →
8.0.1 09 Apr 2020 none MIT — Details →
8.0.0 30 Mar 2020 none MIT — Details →
7.18.2 20 Feb 2020 none MIT — Details →
7.18.1 30 Jan 2020 none MIT — Details →
7.18.0 29 Jan 2020 none MIT — Details →
7.17.1 10 Jan 2020 none MIT — Details →
7.17.0 29 Dec 2019 none MIT — Details →
7.16.1 28 Dec 2019 none MIT — Details →
7.16.0 27 Dec 2019 none MIT — Details →
7.15.2 26 Dec 2019 none MIT — Details →
7.15.1 18 Dec 2019 none MIT — Details →
7.15.0 17 Dec 2019 none MIT — Details →
7.14.0 20 Nov 2019 none MIT — Details →
7.13.0 19 Nov 2019 none MIT — Details →
7.12.1 09 Aug 2019 none MIT — Details →
7.12.0 25 Jul 2019 none MIT — Details →
7.11.0 10 May 2019 none MIT — Details →
7.10.0 16 Apr 2019 none MIT — Details →
7.9.0 15 Mar 2019 none MIT — Details →
7.8.2 07 Mar 2019 none MIT — Details →
7.8.1 20 Feb 2019 none MIT — Details →
7.8.0 11 Jan 2019 none MIT — Details →
7.7.1 29 Nov 2018 none MIT — Details →
7.7.0 29 Nov 2018 none MIT — Details →
7.6.1 07 Nov 2018 none MIT — Details →
7.6.0 26 Oct 2018 none MIT — Details →
7.5.0 03 Oct 2018 none MIT — Details →
7.4.3 07 May 2018 none MIT — Details →
7.4.2 04 May 2018 none MIT — Details →
7.4.1 05 Jan 2018 none MIT — Details →
7.4.0 04 Nov 2017 none MIT — Details →
7.3.0 03 Sep 2017 none MIT — Details →
7.2.0 22 Aug 2017 none MIT — Details →
7.1.2 13 Aug 2017 none MIT — Details →
7.0.3 12 Aug 2017 none MIT — Details →
7.1.1 12 Aug 2017 none MIT — Details →
6.4.2 12 Aug 2017 none MIT — Details →
6.3.3 12 Aug 2017 none MIT — Details →
6.2.5 12 Aug 2017 none MIT — Details →
6.1.6 12 Aug 2017 none MIT — Details →
6.0.5 12 Aug 2017 none MIT — Details →
5.2.1 12 Aug 2017 none MIT — Details →
4.5.7 12 Aug 2017 none MIT — Details →
3.6.4 12 Aug 2017 none MIT — Details →
2.11.2 12 Aug 2017 none — — Details →
7.1.0 04 Aug 2017 none — — Details →
7.0.2 21 Jul 2017 none — — Details →
7.0.1 18 Jul 2017 none — — Details →
7.0.0 18 Jul 2017 none — — Details →
6.4.1 14 Jul 2017 none — — Details →
6.4.0 21 Jun 2017 none — — Details →
6.3.1 20 Jun 2017 none — — Details →
6.3.0 19 Jun 2017 none — — Details →
6.2.4 09 Jun 2017 none — — Details →
6.2.3 24 May 2017 none — — Details →
6.2.2 15 May 2017 none — — Details →
6.1.5 20 Mar 2017 none — — Details →
6.1.4 09 Mar 2017 none — — Details →
6.1.3 06 Mar 2017 none — — Details →
6.1.2 13 Dec 2016 none — — Details →
6.1.1 11 Dec 2016 none — — Details →
6.1.0 11 Aug 2016 none — — Details →
6.0.4 10 Aug 2016 none — — Details →
6.0.3 19 Jul 2016 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for pg

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16082: Remote Code Execution in pg 9.8 critical 2.11.2 24 Jul 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 pg

Is pg safe to use?

Vulert records 1 vulnerabilities for pg in npm: 1 critical, 0 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 pg's Vulert package health score?

Vulert scores pg 84/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. 8.23.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.

Which version of pg should I use?

8.23.1 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?

1 vulnerability is recorded for pg in the npm ecosystem: 1 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, and the oldest entry in this database dates to 24 Jul 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 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.