Skip to main content
VulnerabilityPublished

CVE-2026-133841: flowintel · Missing Authorization

Affects flowintelSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 14:51 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:N/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

CPE configurations (1)

  • cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*

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

AI-suggested

Upgrade FlowIntel to version 4.1.0 or later, where this authorization bypass vulnerability is fixed. No other mitigation actions are indicated by the vendor advisory.

Description

FlowIntel versions prior to 4.1.0 contain an authorization bypass vulnerability in the case serialization logic. Authenticated users with access to any case linked to private cases can view metadata such as identifiers, titles, and descriptions of those private cases without proper authorization. This issue affects multiple access paths including browser views, REST API endpoints, and internal tooling. The vulnerability arises because the serialization method does not verify the requesting user's permissions before including linked-case data in responses.

References

Community reviews

Loading reviews…