<?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>Mon, 05 Oct 2026 13:49:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-31404</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-31404</link>
      <description>EUVD-2026-31404</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-31404</guid>
    </item>
    <item>
      <title>fkie_cve-2021-41037</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-41037</link>
      <description>&lt;p&gt;In Eclipse p2, installable units are able to alter the Eclipse Platform installation and the local machine via touchpoints during installation. Those touchpoints can, for example, alter the command-line used to start the application, injecting things like agent or other settings that usually require particular attention in term of security. Although p2 has built-in strategies to ensure artifacts are signed and then to help establish trust, there is no such strategy for the metadata part that does configure such touchpoints. As a result, it&amp;#39;s possible to install a unit that will run malicious code during installation without user receiving any warning about this installation step being risky when coming from untrusted source.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Eclipse p2, installable units are able to alter the Eclipse Platform installation and the local machine via touchpoints during installation. Those touchpoints can, for example, alter the command-line used to start the application, injecting things like agent or other settings that usually require particular attention in term of security. Although p2 has built-in strategies to ensure artifacts are signed and then to help establish trust, there is no such strategy for the metadata part that does configure such touchpoints. As a result, it&amp;#39;s possible to install a unit that will run malicious code during installation without user receiving any warning about this installation step being risky when coming from untrusted source.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-41037</guid>
    </item>
    <item>
      <title>GHSA-99r4-wvv3-fpr3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-99r4-wvv3-fpr3</link>
      <description>&lt;p&gt;In Eclipse p2, installable units are able to alter the Eclipse Platform installation and the local machine via touchpoints during installation. Those touchpoints can, for example, alter the command-line used to start the application, injecting things like agent or other settings that usually require particular attention in term of security. Although p2 has built-in strategies to ensure artifacts are signed and then to help establish trust, there is no such strategy for the metadata part that does configure such touchpoints. As a result, it&amp;#39;s possible to install a unit that will run malicious code during installation without user receiving any warning about this installation step being risky when coming from untrusted source.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Eclipse p2, installable units are able to alter the Eclipse Platform installation and the local machine via touchpoints during installation. Those touchpoints can, for example, alter the command-line used to start the application, injecting things like agent or other settings that usually require particular attention in term of security. Although p2 has built-in strategies to ensure artifacts are signed and then to help establish trust, there is no such strategy for the metadata part that does configure such touchpoints. As a result, it&amp;#39;s possible to install a unit that will run malicious code during installation without user receiving any warning about this installation step being risky when coming from untrusted source.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-99r4-wvv3-fpr3</guid>
    </item>
    <item>
      <title>gsd-2021-41037</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-41037</link>
      <description>gsd-2021-41037</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-41037</guid>
    </item>
  </channel>
</rss>
