CVE-2026-133001: its duplicate alert ingestion logic · FlowIntel Contains an Authorization Flaw
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 19 Nov 2026, 13:51 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 5.3 |
|---|
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| flowintelflowintel | Affected
| Fixed in– |
GitHubflowintelpkg:github/flowintelOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, administrators should consider manually reviewing and re-scoping alerts to ensure correct ownership and visibility. Monitor vendor communications for updates regarding a fix.
Description
FlowIntel has an authorization flaw in its duplicate alert ingestion logic that causes stale ownership and visibility fields to persist when duplicate alerts are updated. This results in alerts retaining broader visibility scopes than intended, allowing unauthorized users or organizations to access alert content indefinitely until manually re-scoped or deleted. The issue affects all duplicate updates, including alerts in terminal review states and those recovered from uniqueness conflicts. The vulnerability affects versions prior to 4.1.0.