CVE-2017-16082: A remote code execution vulnerability was found within the pg module when the remote database or query specifi

Q: How do I fix CVE-2017-16082?

pg: upgrade to 2.11.2, 3.6.4, 4.5.7, 5.2.1, 6.4.2, 7.1.2. Exact commands for each OS are on this page.

Q: Is CVE-2017-16082 being exploited?

CVE-2017-16082 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-16082 affect?

CVE-2017-16082 affects pg. Severity is critical (CVSS 9.8). A remote code execution vulnerability was found within the pg module when the remote database or query specifies a specially crafted column name. There are 2 likely scenarios in which one would likely be vulnerable. 1) Executing unsafe, use

Q: How urgent is CVE-2017-16082?

Priority 68/100. Critical severity; EPSS top 4%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2017-16082 is a critical-severity flaw (CVSS 9.8) affecting pg. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A remote code execution vulnerability was found within the pg module when the remote database or query specifies a specially crafted column name. There are 2 likely scenarios in which one would likely be vulnerable. 1) Executing unsafe, user-supplied sql which contains a malicious column name. 2) Connecting to an untrusted database and executing a query which returns results where any of the column names are malicious.

Why this priority

Critical severity
EPSS top 4%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	10.4% (top 4%)
CISA exploited list	No
Weakness	CWE-94
Published	2018-06-07
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: node-postgres

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-06-07 02:29 UTCPublished CVE record published
2026-06-17 01:08 UTCUpdated Record last modified

node-postgres pg UPGRADE

Affected: >= 2.0.0 and < 2.11.2 · >= 3.0.0 and < 3.6.4 · >= 4.0.0 and < 4.5.7 · > 5.0.0 and < 5.2.1 · >= 6.0.0 and < 6.4.2 · >= 7.0.0 and < 7.1.2

Fixed in: 2.11.2, 3.6.4, 4.5.7, 5.2.1, 6.4.2, 7.1.2

Safe to downgrade to: a release before 2.0.0

1. Check installed version

npm ls pg

2. UPGRADE to 2.11.2

npm install pg@">=2.11.2"

3. If no update is available yet, DOWNGRADE to a release before 2.0.0

npm view pg versions npm install pg@"<2.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-16082?

pg: upgrade to 2.11.2, 3.6.4, 4.5.7, 5.2.1, 6.4.2, 7.1.2. Exact commands for each OS are on this page.

Is CVE-2017-16082 being exploited?

CVE-2017-16082 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-16082 affect?

CVE-2017-16082 affects pg. Severity is critical (CVSS 9.8). A remote code execution vulnerability was found within the pg module when the remote database or query specifies a specially crafted column name. There are 2 likely scenarios in which one would likely be vulnerable. 1) Executing unsafe, use

How urgent is CVE-2017-16082?

Priority 68/100. Critical severity; EPSS top 4%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PostgreSQL vulnerabilities

Related CVEs

CVE-2024-44905 MEDIUM 6.5 DOWNGRADE go-pg pg v10.13.0 was discovered to contain a SQL injection vulnerability via the component /types/append_valu

References

← Back to latest CVEs