Skip to main content
VulnerabilityPublished

CVE-2026-133652: Flowintel , contained a session management vulnerability in its browser authentication mechanism

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133652· High 7.2

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

Data as of 20 Nov 2026, 13:49 UTC

CVSS 4.0 base score
7.2High
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.2
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/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

If you cannot patch yet, users should be cautious about session security and consider invalidating sessions manually if possible. Administrators should monitor for suspicious session activity. Avoid exposure to session theft vectors such as XSS and network interception.

Description

Flowintel versions prior to 4.1.0 contain a session management vulnerability in their browser authentication mechanism. The session identifier uses a bare numeric user ID instead of a credential-bound token, leading to multiple weaknesses including persistent remember-me cookies after password changes, lack of session ID rotation on login, and insufficient verification for self-service credential changes. An attacker with a valid session or cookie can maintain unauthorized access and take over accounts by changing credentials without knowing the current password.

References

Community reviews

Loading reviews…