{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "0"
                  },
                  {
                    "last_affected": "4.0.0"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              },
              {
                "range": [
                  {
                    "fixed": "c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362"
                  }
                ],
                "source": "REFERENCES_COMMIT"
              }
            ]
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "6a6e56af53232fc6a119f7b8a8a24ab5d5d0b729"
            },
            {
              "fixed": "c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362"
            }
          ],
          "repo": "https://github.com/flowintel/flowintel",
          "type": "GIT"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "CIRCL",
    "cwe_ids": [
      "CWE-668",
      "CWE-862"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/133xxx/CVE-2026-133001.json"
  },
  "details": "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.\n\nThis 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.\n\nSecurity impact:\n- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.\n- Stale access persists indefinitely until the alert is independently re-scoped or deleted.\n\nAffected version: \u003c4.1.0.",
  "id": "CVE-2026-133001",
  "modified": "2026-11-19T18:45:28.722620244Z",
  "published": "2026-11-19T10:35:06.740Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/133xxx/CVE-2026-133001.json"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/flowintel/flowintel"
    },
    {
      "type": "FIX",
      "url": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-133001"
    }
  ],
  "schema_version": "1.9.2",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion"
}