Is pg 6.2 vulnerable?

npm · 4 releases from 6.2.2 to 6.2.5 · latest pg is 8.23.1 · checked 2 Nov 2026

No known advisories in the last release

pg 6.2.5, the last 6.2 release, has no known advisories. 1 advisory affects earlier 6.2.x releases, so update to 6.2.5.

Update within 6.2:npm install pg@6.2.5

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Fixed within 6.2.x, affecting earlier releases

  • CriticalCVE-2017-16082GHSA-wc9v-mj63-m9g524 Jul 2018

    Remote Code Execution in pg

    Affected
    <2.11.2 · >=3.0.0 <3.6.4 · >=4.0.0 <4.5.7 · >=5.0.0 <5.2.1 · >=6.0.0 <6.0.5 · >=6.1.0 <6.1.6 · >=6.2.0 <6.2.5 · >=6.3.0 <6.3.3 · >=6.4.0 <6.4.2 · >=7.0.0 <7.0.2 · >=7.1.0 <7.1.2
    Fixed in
    2.11.2, 3.6.4, 4.5.7, 5.2.1, 6.0.5, 6.1.6, 6.2.5, 6.3.3, 6.4.2, 7.0.2, 7.1.2

Which of your client projects are still on pg 6.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact pg version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other pg versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.