Skip to main content
VulnerabilityPublished

CVE-2026-133849: Vulnerability Exists

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133849· High 7.1

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

Data as of 20 Nov 2026, 16:04 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

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 that enforces case visibility checks in calendar queries. Users should upgrade to version 4.1.0 or later to remediate this vulnerability. No other mitigation or temporary workaround is indicated.

Description

A vulnerability in the flowintel application's calendar functionality allowed unauthorized users to access private case data. The calendar queries did not enforce visibility checks on parent cases, exposing tasks assigned to users or their organizations without verifying permission. This led to potential information disclosure of private cases. The issue affected task visibility logic and assigned-only task queries. A fix has been implemented to recheck case visibility alongside task assignment and organization membership, preventing unauthorized data exposure. The vulnerability affects flowintel versions prior to 4.1.0.

References

Community reviews

Loading reviews…