CVE-2026-133648: flowintel · Improper Certificate Validation
Affects flowintelSource CVE Database V5
Not known to be exploited · CVSS 9.9 Critical : upgrade to 4.1.0 as a priority.
Data as of 20 Nov 2026, 10:36 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 9.9 |
|---|
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| flowintelflowintel | Affected
| Fixed in
|
GitHubflowintelpkg:github/flowintelOther threats | Affected
| Fixed in
|
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 proper TLS certificate validation is enforced for MISP API, SMTP STARTTLS, and IMAP TLS connections. This update fixes the improper certificate validation vulnerability. No additional mitigation is required once the software is updated.
Description
Flowintel versions prior to 4.1.0 improperly disabled TLS certificate verification for MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This vulnerability allowed a man-in-the-middle attacker to impersonate remote servers, intercept sensitive data including API keys and mail credentials, and modify threat intelligence data exchanged. Exploitation required no authentication and no user interaction, only network positioning between Flowintel and its MISP or mail servers. The issue is fixed in Flowintel 4.1.0.