<?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-11-17T19:00:23.304134+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-123723</id>
    <title>EUVD-2026-123723</title>
    <updated>2026-11-17T19:00:23.307414+00:00</updated>
    <content>EUVD-2026-123723</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-123723"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2009-2940</id>
    <title>fkie_cve-2009-2940</title>
    <updated>2026-11-17T19:00:23.307448+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The pygresql module 3.8.1 and 4.0 for Python does not properly support the PQescapeStringConn function, which might allow remote attackers to leverage escaping issues involving multibyte character encodings.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2009-2940"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xv6x-43gq-4hfj</id>
    <title>GHSA-xv6x-43gq-4hfj — PyGreSQL Might Be Vulnerable to Encoding-Based SQL Injection</title>
    <updated>2026-11-17T19:00:23.307479+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: PyGreSQL</p>
<p>PyGreSQL 3.8 did not use PostgreSQL’s safe `string` and `bytea` functions in its own escaping functions. As a result, applications written to use PyGreSQL’s escaping functions are vulnerable to SQL injections when processing certain multi-byte character sequences. Because the safe functions require a database connection, to maintain backwards compatibility, `pg.escape_string()` and `pg.escape_bytea()` are still available, but applications will have to be adjusted to use the new `pyobj.escape_string()` and `pyobj.escape_bytea()` functions. For example, code containing:</p>
<p>```python
import pg
connection = pg.connect(...)
escaped = pg.escape_string(untrusted_input)
```
should be adjusted to use:</p>
<p>```python
import pg
connection = pg.connect(...)
escaped = connection.escape_string(untrusted_input)
```</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xv6x-43gq-4hfj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2009-2940</id>
    <title>gsd-2009-2940</title>
    <updated>2026-11-17T19:00:23.307514+00:00</updated>
    <content>gsd-2009-2940</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2009-2940"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2009-18</id>
    <title>PYSEC-2009-18</title>
    <updated>2026-11-17T19:00:23.307527+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pygresql</p>
<p>The pygresql module 3.8.1 and 4.0 for Python does not properly support the PQescapeStringConn function, which might allow remote attackers to leverage escaping issues involving multibyte character encodings.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2009-18"/>
  </entry>
</feed>
