<?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, 10 Oct 2026 16:42:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-60125 — importModule function in MISP ignores per-organisation import module restrictions</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-60125</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; misp&lt;/p&gt;
&lt;p&gt;MISP’s importModule() path used getEnabledModule() to resolve a single import module by name, but this lookup did not enforce the per-organisation module restriction checked by getEnabledModules(). As a result, an authenticated user from an organisation that was not allowed to use a module restricted via Plugin.Import_&amp;lt;module&amp;gt;_restrict could still invoke that import module directly if they knew its name.&lt;/p&gt;
&lt;p&gt;This could allow unauthorised access to restricted import-module functionality and, depending on the module and the user’s event permissions, may allow unauthorised import or modification of event data through a module that should have been unavailable to the user’s organisation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; misp&lt;/p&gt;
&lt;p&gt;MISP’s importModule() path used getEnabledModule() to resolve a single import module by name, but this lookup did not enforce the per-organisation module restriction checked by getEnabledModules(). As a result, an authenticated user from an organisation that was not allowed to use a module restricted via Plugin.Import_&amp;lt;module&amp;gt;_restrict could still invoke that import module directly if they knew its name.&lt;/p&gt;
&lt;p&gt;This could allow unauthorised access to restricted import-module functionality and, depending on the module and the user’s event permissions, may allow unauthorised import or modification of event data through a module that should have been unavailable to the user’s organisation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-60125</guid>
    </item>
  </channel>
</rss>
