<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-24T15:19:10.341691+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-184637</id>
    <title>EUVD-2026-184637</title>
    <updated>2026-10-24T15:19:10.344924+00:00</updated>
    <content>EUVD-2026-184637</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-184637"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2017-16082</id>
    <title>fkie_cve-2017-16082</title>
    <updated>2026-10-24T15:19:10.344955+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2017-16082"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wc9v-mj63-m9g5</id>
    <title>GHSA-wc9v-mj63-m9g5 — Remote Code Execution in pg</title>
    <updated>2026-10-24T15:19:10.344987+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: pg</p>
<p>Affected versions of `pg` contain a remote code execution vulnerability that occurs when the remote database or query specifies a crafted column name.</p>
<p>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.</p>
<p>## Proof of Concept
```
const { Client } = require('pg')
const client = new Client()
client.connect()</p>
<p>const sql = `SELECT 1 AS "\\'/*", 2 AS "\\'*/\n + console.log(process.env)] = null;\n//"`</p>
<p>client.query(sql, (err, res) =&gt; {
  client.end()
})
```</p>
<p>## Recommendation</p>
<p>* 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. )</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wc9v-mj63-m9g5"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2017-16082</id>
    <title>gsd-2017-16082</title>
    <updated>2026-10-24T15:19:10.345027+00:00</updated>
    <content>gsd-2017-16082</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2017-16082"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-16082</id>
    <title>UBUNTU-CVE-2017-16082</title>
    <updated>2026-10-24T15:19:10.345040+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: node-postgres</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-16082"/>
  </entry>
</feed>
