<?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:05 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-133001</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-133001</link>
      <description>&lt;p&gt;FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector&amp;#39;s current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector&amp;#39;s scope was narrowed or changed.&lt;/p&gt;
&lt;p&gt;This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.&lt;/p&gt;
&lt;p&gt;Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.&lt;/p&gt;
&lt;p&gt;Affected version: &amp;lt;4.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector&amp;#39;s current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector&amp;#39;s scope was narrowed or changed.&lt;/p&gt;
&lt;p&gt;This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.&lt;/p&gt;
&lt;p&gt;Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.&lt;/p&gt;
&lt;p&gt;Affected version: &amp;lt;4.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-133001</guid>
    </item>
    <item>
      <title>gcve-1-2026-20317 — FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion</title>
      <link>https://db.gcve.eu/vuln/gcve-1-2026-20317</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; flowintel&lt;/p&gt;
&lt;p&gt;FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector&amp;#39;s current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector&amp;#39;s scope was narrowed or changed.&lt;/p&gt;
&lt;p&gt;This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.&lt;/p&gt;
&lt;p&gt;Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.&lt;/p&gt;
&lt;p&gt;Affected version: &amp;lt;4.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; flowintel&lt;/p&gt;
&lt;p&gt;FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector&amp;#39;s current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector&amp;#39;s scope was narrowed or changed.&lt;/p&gt;
&lt;p&gt;This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.&lt;/p&gt;
&lt;p&gt;Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.&lt;/p&gt;
&lt;p&gt;Affected version: &amp;lt;4.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/gcve-1-2026-20317</guid>
    </item>
    <item>
      <title>GHSA-8hmx-g4j7-9cc3</title>
      <link>https://db.gcve.eu/vuln/ghsa-8hmx-g4j7-9cc3</link>
      <description>&lt;p&gt;FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector&amp;#39;s current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector&amp;#39;s scope was narrowed or changed.&lt;/p&gt;
&lt;p&gt;This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.&lt;/p&gt;
&lt;p&gt;Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.&lt;/p&gt;
&lt;p&gt;Affected version: &amp;lt;4.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector&amp;#39;s current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector&amp;#39;s scope was narrowed or changed.&lt;/p&gt;
&lt;p&gt;This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.&lt;/p&gt;
&lt;p&gt;Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.&lt;/p&gt;
&lt;p&gt;Affected version: &amp;lt;4.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8hmx-g4j7-9cc3</guid>
    </item>
  </channel>
</rss>
