Skip to main content
VulnerabilityPublished

CVE-2026-133851: FlowIntel's alerting module contained an authorization bypass in the alert access control logic

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133851· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.1.0 when convenient.

Data as of 20 Nov 2026, 16:05 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CIRCL)CVSS 4.05.3
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade flowintel to 4.1.0.

Affected software

ProductAffectedFixed in
flowintelflowintelAffected
  • <4.1.0
Fixed in
  • 4.1.0
GitHubflowintelpkg:github/flowintelOther threatsAffected
  • <4.1.0
Fixed in
  • 4.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in FlowIntel version 4.1.0 and later. Users should upgrade to version 4.1.0 or above to remediate this authorization bypass vulnerability. Until upgraded, restrict connector ownership assignments carefully and monitor for unauthorized access. No vendor advisory or patch links were provided, so verify with the vendor for official remediation guidance.

Description

FlowIntel's alerting module had an authorization bypass vulnerability in its alert access control logic prior to version 4.1.0. The system incorrectly relied only on connector ownership to grant access to alerts linked to private cases, without verifying if the user was still a valid member of the private case. This allowed unauthorized users to view sensitive alert details and modify alert statuses or create cases from alerts they should not access. Additionally, a time-of-check to time-of-use (TOCTOU) race condition could expose private case identifiers to unauthorized users during concurrent operations.

References

Community reviews

Loading reviews…