<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T23:02:56.649484+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-107175</id>
    <title>fkie_cve-2026-107175</title>
    <updated>2026-10-08T23:02:56.809306+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>MISP contains a defect in its event save workflow that prevents the correlation engine from recalculating correlations when an event's distribution level or sharing group is modified.</p>
<p>When a user edits an existing event and changes its distribution or sharing_group_id, the internal before-save hook stored the incoming (new) data rather than the previously persisted values. As a result, the after-save comparison that determines whether a correlation refresh is needed never detected the change, and stale correlations persisted.</p>
<p>Security impact:</p>
<p>- Stale correlations may continue to expose event data to users in a broader sharing group after the event has been moved to a more restrictive group, resulting in unintended information disclosure.</p>
<p>- Conversely, newly relevant correlations may not appear after a distribution widening, degrading the completeness of threat intelligence sharing.</p>
<p>Preconditions:</p>
<p>- An authenticated user with write access to at least one MISP event.</p>
<p>- The user modifies the event's distribution or sharing_group_id field.</p>
<p>Affected versions: &lt;2.5.48</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-107175"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/gcve-1-2026-20264</id>
    <title>GCVE-1-2026-20264 — MISP Correlation Engine Fails to Refresh When Event Distribution or Sharing Group Changes</title>
    <updated>2026-10-08T23:02:56.809434+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> MISP</p>
<p>MISP contains a defect in its event save workflow that prevents the correlation engine from recalculating correlations when an event's distribution level or sharing group is modified.</p>
<p>When a user edits an existing event and changes its distribution or sharing_group_id, the internal before-save hook stored the incoming (new) data rather than the previously persisted values. As a result, the after-save comparison that determines whether a correlation refresh is needed never detected the change, and stale correlations persisted.</p>
<p>Security impact:</p>
<p>- Stale correlations may continue to expose event data to users in a broader sharing group after the event has been moved to a more restrictive group, resulting in unintended information disclosure.</p>
<p>- Conversely, newly relevant correlations may not appear after a distribution widening, degrading the completeness of threat intelligence sharing.</p>
<p>Preconditions:</p>
<p>- An authenticated user with write access to at least one MISP event.</p>
<p>- The user modifies the event's distribution or sharing_group_id field.</p>
<p>Affected versions: &lt;2.5.48</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/gcve-1-2026-20264"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-9v45-rw9g-683m</id>
    <title>GHSA-9v45-rw9g-683m</title>
    <updated>2026-10-08T23:02:56.809518+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>MISP contains a defect in its event save workflow that prevents the correlation engine from recalculating correlations when an event's distribution level or sharing group is modified.</p>
<p>When a user edits an existing event and changes its distribution or sharing_group_id, the internal before-save hook stored the incoming (new) data rather than the previously persisted values. As a result, the after-save comparison that determines whether a correlation refresh is needed never detected the change, and stale correlations persisted.</p>
<p>Security impact:</p>
<p>- Stale correlations may continue to expose event data to users in a broader sharing group after the event has been moved to a more restrictive group, resulting in unintended information disclosure.</p>
<p>- Conversely, newly relevant correlations may not appear after a distribution widening, degrading the completeness of threat intelligence sharing.</p>
<p>Preconditions:</p>
<p>- An authenticated user with write access to at least one MISP event.</p>
<p>- The user modifies the event's distribution or sharing_group_id field.</p>
<p>Affected versions: &lt;2.5.48</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-9v45-rw9g-683m"/>
  </entry>
</feed>
