Skip to main content
VulnerabilityPublished

CVE-2026-133853: flowintel · Authentication Bypass by Spoofing

Affects flowintelSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 15:08 UTC

CVSS 4.0 base score
6.0Medium
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.06.0
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/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

A fix is available in FlowIntel version 4.1.0. Users should upgrade to version 4.1.0 or later to remediate this vulnerability. No other mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-133853 is an authentication bypass vulnerability in FlowIntel's chatbot component prior to version 4.1.0. The flaw arises because the system uses a single shared MCP session and a process-wide environment variable to pass per-user API credentials, causing credentials to be shared across concurrent requests. This can lead to unauthorized access where a lower-privilege user may access data belonging to a higher-privilege user, and invalidated sessions may still operate under stale credentials.

References

Community reviews

Loading reviews…