<?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://vulnerability.circl.lu</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>Thu, 08 Oct 2026 12:34:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-107278 — MISP Object Sync Drops Objects and Attributes When Description Is Empty</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-107278</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MISP&lt;/p&gt;
&lt;p&gt;MISP contains a validation flaw in its object synchronization logic. When a MISP Object is created without a description, it is stored correctly on the originating instance. However, when that object is replicated to another MISP instance via the sync mechanism, the receiving instance&amp;#39;s validation rule rejects the object because the description field is empty. As a result, the receiving instance silently drops the object along with all of its associated attributes, leading to loss of threat-intelligence data.&lt;/p&gt;
&lt;p&gt;Preconditions:&lt;/p&gt;
&lt;p&gt;- Two or more MISP instances are configured to synchronize objects.&lt;/p&gt;
&lt;p&gt;- A user with object-creation privileges creates an object without supplying a description.&lt;/p&gt;
&lt;p&gt;- The object is subsequently synced to a peer instance.&lt;/p&gt;
&lt;p&gt;Impact:&lt;/p&gt;
&lt;p&gt;- Valid objects and their attributes are silently discarded on receiving instances, causing data-integrity loss in the threat-intelligence pipeline.&lt;/p&gt;
&lt;p&gt;- The issue is not externally exploitable in a traditional sense but can be triggered by any authorized user who creates objects without descriptions, resulting in unintended data loss across the sync topology.&lt;/p&gt;
&lt;p&gt;Affected: &amp;lt;2.5.48.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MISP&lt;/p&gt;
&lt;p&gt;MISP contains a validation flaw in its object synchronization logic. When a MISP Object is created without a description, it is stored correctly on the originating instance. However, when that object is replicated to another MISP instance via the sync mechanism, the receiving instance&amp;#39;s validation rule rejects the object because the description field is empty. As a result, the receiving instance silently drops the object along with all of its associated attributes, leading to loss of threat-intelligence data.&lt;/p&gt;
&lt;p&gt;Preconditions:&lt;/p&gt;
&lt;p&gt;- Two or more MISP instances are configured to synchronize objects.&lt;/p&gt;
&lt;p&gt;- A user with object-creation privileges creates an object without supplying a description.&lt;/p&gt;
&lt;p&gt;- The object is subsequently synced to a peer instance.&lt;/p&gt;
&lt;p&gt;Impact:&lt;/p&gt;
&lt;p&gt;- Valid objects and their attributes are silently discarded on receiving instances, causing data-integrity loss in the threat-intelligence pipeline.&lt;/p&gt;
&lt;p&gt;- The issue is not externally exploitable in a traditional sense but can be triggered by any authorized user who creates objects without descriptions, resulting in unintended data loss across the sync topology.&lt;/p&gt;
&lt;p&gt;Affected: &amp;lt;2.5.48.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-107278</guid>
    </item>
  </channel>
</rss>
