CVE-2017-16082
A remote code execution vulnerability was found within the pg module when the remote database or query specifies a specially crafted column name.
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 10.4%, higher than 96% of all known CVEs. Patch or mitigate before the next change window.
Description
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.
- CVSS 3.0
- 9.8 CRITICALCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 10.45% probability · 96th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-94
- Affected
- node-postgres/pg
- Source
- support@hackerone.com
EPSS moved from 7.1% on 21 September 2026 to 10.4% on 27 October 2026, peaking at 10.5% on 22 September 2026. The dashed line is the ten per cent mark our analysts treat as “patch before the next change window”.
References
- https://node-postgres.com/announcements#2017-08-12-code-execution-vulnerabilityExploit, Third Party Advisory
- https://nodesecurity.io/advisories/521Exploit, Third Party Advisory
- https://node-postgres.com/announcements#2017-08-12-code-execution-vulnerabilityExploit, Third Party Advisory
- https://nodesecurity.io/advisories/521Exploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.