<?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>Wed, 07 Oct 2026 04:28:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-86417 — MISP Dashboard Template REST API Exposes Template Owner Email Addresses to Unauthorized Users</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-86417</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MISP&lt;/p&gt;
&lt;p&gt;Affected versions of MISP inconsistently enforced email-address visibility in DashboardsController::listTemplates().&lt;/p&gt;
&lt;p&gt;The query always fetched User.email, while redaction happened only inside the non-REST rendering branch. As a result, the same authenticated user who saw redacted data in the normal HTML interface could request the REST/JSON representation and receive template owners’ email addresses without the intended privilege check.&lt;/p&gt;
&lt;p&gt;The fix moves the decision to a centralized User::canSeeEmails() authorization helper. Email addresses are now fetched only when the requester is a site administrator or the instance explicitly enables Security.disclose_user_emails. The same helper is also reused by other dashboard widgets to keep email-disclosure policy consistent.&lt;/p&gt;
&lt;p&gt;Version affected: ≤2.5.45&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MISP&lt;/p&gt;
&lt;p&gt;Affected versions of MISP inconsistently enforced email-address visibility in DashboardsController::listTemplates().&lt;/p&gt;
&lt;p&gt;The query always fetched User.email, while redaction happened only inside the non-REST rendering branch. As a result, the same authenticated user who saw redacted data in the normal HTML interface could request the REST/JSON representation and receive template owners’ email addresses without the intended privilege check.&lt;/p&gt;
&lt;p&gt;The fix moves the decision to a centralized User::canSeeEmails() authorization helper. Email addresses are now fetched only when the requester is a site administrator or the instance explicitly enables Security.disclose_user_emails. The same helper is also reused by other dashboard widgets to keep email-disclosure policy consistent.&lt;/p&gt;
&lt;p&gt;Version affected: ≤2.5.45&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-86417</guid>
    </item>
  </channel>
</rss>
