<?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 09:35:30 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-225280</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-225280</link>
      <description>EUVD-2026-225280</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-225280</guid>
    </item>
    <item>
      <title>fkie_cve-2022-3913</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-3913</link>
      <description>&lt;p&gt;Rapid7 Nexpose and InsightVM versions 6.6.82 through 6.6.177 fail to validate the certificate of the update server when downloading updates. This failure could allow an attacker in a privileged position on the network to provide their own HTTPS endpoint, or intercept communications to the legitimate endpoint. The attacker would need some pre-existing access to at least one node on the network path between the Rapid7-controlled update server and the Nexpose/InsightVM application, and the ability to either spoof the update server&amp;#39;s FQDN or redirect legitimate traffic to the attacker&amp;#39;s server in order to exploit this vulnerability. Note that even in this scenario, an attacker could not normally replace an update package with a malicious package, since the update process validates a separate, code-signing certificate, distinct from the HTTPS certificate used for communication. This issue was resolved on February 1, 2023 in update 6.6.178 of Nexpose and InsightVM.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Rapid7 Nexpose and InsightVM versions 6.6.82 through 6.6.177 fail to validate the certificate of the update server when downloading updates. This failure could allow an attacker in a privileged position on the network to provide their own HTTPS endpoint, or intercept communications to the legitimate endpoint. The attacker would need some pre-existing access to at least one node on the network path between the Rapid7-controlled update server and the Nexpose/InsightVM application, and the ability to either spoof the update server&amp;#39;s FQDN or redirect legitimate traffic to the attacker&amp;#39;s server in order to exploit this vulnerability. Note that even in this scenario, an attacker could not normally replace an update package with a malicious package, since the update process validates a separate, code-signing certificate, distinct from the HTTPS certificate used for communication. This issue was resolved on February 1, 2023 in update 6.6.178 of Nexpose and InsightVM.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-3913</guid>
    </item>
    <item>
      <title>GHSA-v4h7-r9v8-hp3g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v4h7-r9v8-hp3g</link>
      <description>&lt;p&gt;Rapid7 Nexpose and InsightVM versions 6.6.82 through 6.6.177 fail to validate the certificate of the update server when downloading updates. This failure could allow an attacker in a privileged position on the network to provide their own HTTPS endpoint, or intercept communications to the legitimate endpoint. The attacker would need some pre-existing access to at least one node on the network path between the Rapid7-controlled update server and the Nexpose/InsightVM application, and the ability to either spoof the update server&amp;#39;s FQDN or redirect legitimate traffic to the attacker&amp;#39;s server in order to exploit this vulnerability. Note that even in this scenario, an attacker could not normally replace an update package with a malicious package, since the update process validates a separate, code-signing certificate, distinct from the HTTPS certificate used for communication. This issue was resolved on February 1, 2023 in update 6.6.178 of Nexpose and InsightVM.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Rapid7 Nexpose and InsightVM versions 6.6.82 through 6.6.177 fail to validate the certificate of the update server when downloading updates. This failure could allow an attacker in a privileged position on the network to provide their own HTTPS endpoint, or intercept communications to the legitimate endpoint. The attacker would need some pre-existing access to at least one node on the network path between the Rapid7-controlled update server and the Nexpose/InsightVM application, and the ability to either spoof the update server&amp;#39;s FQDN or redirect legitimate traffic to the attacker&amp;#39;s server in order to exploit this vulnerability. Note that even in this scenario, an attacker could not normally replace an update package with a malicious package, since the update process validates a separate, code-signing certificate, distinct from the HTTPS certificate used for communication. This issue was resolved on February 1, 2023 in update 6.6.178 of Nexpose and InsightVM.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v4h7-r9v8-hp3g</guid>
    </item>
    <item>
      <title>gsd-2022-3913</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-3913</link>
      <description>gsd-2022-3913</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-3913</guid>
    </item>
  </channel>
</rss>
