<?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>Sun, 04 Oct 2026 09:00:36 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-349414</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-349414</link>
      <description>EUVD-2026-349414</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-349414</guid>
    </item>
    <item>
      <title>fkie_cve-2026-17603</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-17603</link>
      <description>&lt;p&gt;Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set through the DataStore configuration API. A user holding the nx-datastores-update permission could set the connectionInitSql property to execute arbitrary SQL against the configured database on every new connection. On the default H2 database backend, this could be leveraged to achieve remote code execution as the Nexus process user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set through the DataStore configuration API. A user holding the nx-datastores-update permission could set the connectionInitSql property to execute arbitrary SQL against the configured database on every new connection. On the default H2 database backend, this could be leveraged to achieve remote code execution as the Nexus process user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-17603</guid>
    </item>
    <item>
      <title>GHSA-65xx-g4qc-4g4m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-65xx-g4qc-4g4m</link>
      <description>&lt;p&gt;Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set through the DataStore configuration API. A user holding the nx-datastores-update permission could set the connectionInitSql property to execute arbitrary SQL against the configured database on every new connection. On the default H2 database backend, this could be leveraged to achieve remote code execution as the Nexus process user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set through the DataStore configuration API. A user holding the nx-datastores-update permission could set the connectionInitSql property to execute arbitrary SQL against the configured database on every new connection. On the default H2 database backend, this could be leveraged to achieve remote code execution as the Nexus process user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-65xx-g4qc-4g4m</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2713 — Sonatype Nexus Repository Manager: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2713</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Sonatype Nexus Repository Manager ausnutzen, um Daten offenzulegen oder zu Manipulieren, Code auszuführen oder Rechte zu erweitern.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Sonatype Nexus Repository Manager ausnutzen, um Daten offenzulegen oder zu Manipulieren, Code auszuführen oder Rechte zu erweitern.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2713</guid>
    </item>
  </channel>
</rss>
