<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 00:20:07 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-177727</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-177727</link>
      <description>EUVD-2026-177727</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-177727</guid>
    </item>
    <item>
      <title>fkie_cve-2016-10553</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2016-10553</link>
      <description>&lt;p&gt;sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS. A fix was pushed out that fixed potential SQL injection in sequelize 2.1.3 and earlier.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS. A fix was pushed out that fixed potential SQL injection in sequelize 2.1.3 and earlier.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2016-10553</guid>
    </item>
    <item>
      <title>GHSA-2v7q-2xqx-f4q5 — Potential SQL Injection in sequelize</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2v7q-2xqx-f4q5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: sequelize&lt;/p&gt;
&lt;p&gt;Affected versions of `sequelize` are vulnerable to SQL Injection when user input is passed into `findOne` or into a statement such as `where: &amp;#34;user input&amp;#34;`.&lt;/p&gt;
&lt;p&gt;## Recommendation&lt;/p&gt;
&lt;p&gt;Update to version 3.0.0 or later.&lt;/p&gt;
&lt;p&gt;Version 3.0.0 will introduce a number of breaking changes.
Thankfully, the project authors have provided a 2.x -&amp;gt; 3.x [upgrade guide](https://github.com/sequelize/sequelize/wiki/Upgrade-from-2.0-to-3.0) to ease this transition.&lt;/p&gt;
&lt;p&gt;If upgrading is not an option, it is also possible to mitigate this by ensuring that all uses of `where: &amp;#34;input&amp;#34;` and `findOne(&amp;#34;input&amp;#34;)` are properly sanitized, such as by the use of a wrapper function.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: sequelize&lt;/p&gt;
&lt;p&gt;Affected versions of `sequelize` are vulnerable to SQL Injection when user input is passed into `findOne` or into a statement such as `where: &amp;#34;user input&amp;#34;`.&lt;/p&gt;
&lt;p&gt;## Recommendation&lt;/p&gt;
&lt;p&gt;Update to version 3.0.0 or later.&lt;/p&gt;
&lt;p&gt;Version 3.0.0 will introduce a number of breaking changes.
Thankfully, the project authors have provided a 2.x -&amp;gt; 3.x [upgrade guide](https://github.com/sequelize/sequelize/wiki/Upgrade-from-2.0-to-3.0) to ease this transition.&lt;/p&gt;
&lt;p&gt;If upgrading is not an option, it is also possible to mitigate this by ensuring that all uses of `where: &amp;#34;input&amp;#34;` and `findOne(&amp;#34;input&amp;#34;)` are properly sanitized, such as by the use of a wrapper function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2v7q-2xqx-f4q5</guid>
    </item>
    <item>
      <title>gsd-2016-10553</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2016-10553</link>
      <description>gsd-2016-10553</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2016-10553</guid>
    </item>
  </channel>
</rss>
