<?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-11-19T22:49:55.081531+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/fkie_cve-2026-133001</id>
    <title>fkie_cve-2026-133001</title>
    <updated>2026-11-19T22:49:55.083320+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>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'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's scope was narrowed or changed.</p>
<p>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.</p>
<p>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.</p>
<p>Affected version: &lt;4.1.0.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-133001"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/gcve-1-2026-20317</id>
    <title>gcve-1-2026-20317 — FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion</title>
    <updated>2026-11-19T22:49:55.083416+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> flowintel</p>
<p>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'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's scope was narrowed or changed.</p>
<p>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.</p>
<p>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.</p>
<p>Affected version: &lt;4.1.0.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/gcve-1-2026-20317"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-8hmx-g4j7-9cc3</id>
    <title>GHSA-8hmx-g4j7-9cc3</title>
    <updated>2026-11-19T22:49:55.083459+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>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'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's scope was narrowed or changed.</p>
<p>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.</p>
<p>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.</p>
<p>Affected version: &lt;4.1.0.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-8hmx-g4j7-9cc3"/>
  </entry>
</feed>
