<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-21T11:33:43.613865+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-112179</id>
    <title>CVE-2026-112179 — MISP Event Synchronization Exposes Non-Exportable Tags on Remote Instances</title>
    <updated>2026-10-21T11:33:43.615794+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> MISP</p>
<p>In MISP, the event synchronization process contained a logic error in the preparation of event reports for remote push. The filtering of non-exportable tags was applied only once after the iteration over all reports, rather than to each individual report.</p>
<p>As a result:</p>
<p>- All reports except the last one in the set were pushed to the remote MISP instance with their non-exportable tags intact, effectively disclosing restricted tag information to the receiving instance.</p>
<p>- When the last report in the set was withheld (empty), a null report was pushed, causing the remote instance to fail saving the event.</p>
<p>This issue affects any MISP instance configured to push events with multiple reports to a remote server via synchronization.</p>
<p>Affected: &lt;2.5.48.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-112179"/>
  </entry>
</feed>
