<?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://db.gcve.eu</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, 19 Nov 2026 22:57:00 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-132643</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-132643</link>
      <description>&lt;p&gt;MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter&amp;#39;s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation&amp;#39;s ID in the filter. The query would then return only that organisation&amp;#39;s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter&amp;#39;s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation&amp;#39;s ID in the filter. The query would then return only that organisation&amp;#39;s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-132643</guid>
    </item>
    <item>
      <title>gcve-1-2026-20282 — MISP Anonymised Sightings Reporter Identity Disclosure via Organisation Filter</title>
      <link>https://db.gcve.eu/vuln/gcve-1-2026-20282</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; misp&lt;/p&gt;
&lt;p&gt;MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter&amp;#39;s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation&amp;#39;s ID in the filter. The query would then return only that organisation&amp;#39;s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.&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 an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter&amp;#39;s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation&amp;#39;s ID in the filter. The query would then return only that organisation&amp;#39;s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/gcve-1-2026-20282</guid>
    </item>
    <item>
      <title>GHSA-qmpj-rw2f-69jj</title>
      <link>https://db.gcve.eu/vuln/ghsa-qmpj-rw2f-69jj</link>
      <description>&lt;p&gt;MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter&amp;#39;s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation&amp;#39;s ID in the filter. The query would then return only that organisation&amp;#39;s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter&amp;#39;s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation&amp;#39;s ID in the filter. The query would then return only that organisation&amp;#39;s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qmpj-rw2f-69jj</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4669 — MISP: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4669</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in MISP ausnutzen, um seine Privilegien zu erhöhen, um Informationen offenzulegen, um Dateien zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in MISP ausnutzen, um seine Privilegien zu erhöhen, um Informationen offenzulegen, um Dateien zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4669</guid>
    </item>
  </channel>
</rss>
