Skip to main content
VulnerabilityPublished

CVE-2026-133849: flowintel · Insecure Direct Object Reference

Affects flowintelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 4.1.0 soon.

Data as of 20 Nov 2026, 15:03 UTC

CVSS 4.0 base score
7.1High
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.07.1
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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 the vulnerability is fixed by enforcing case visibility checks in calendar task queries. No other mitigation is indicated or required.

Description

CVE-2026-133849 is a high-severity authorization bypass vulnerability in flowintel's calendar functionality prior to version 4.1.0. The flaw allowed users to view tasks in calendar views without proper verification of their permission to access the parent case, potentially exposing private case data. The issue was fixed in flowintel 4.1.0 by enforcing case visibility checks alongside task assignment and organization membership.

References

Community reviews

Loading reviews…