pg vulnerabilities

PostgreSQL client - pure javascript & libpq with the same API

Registry: npm
Latest: 8.23.1
License: MIT
Source: github.com/brianc/node-postgres (opens the source repository in a new tab)

1 known advisory

The latest version, 8.23.1, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install pg@8.23.1

Check the version you use

Security advisories for pg

CriticalGHSA-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 still run an old pg?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

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

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.