CVE-2026-133648: Flowintel Disables TLS Certificate Verification for MISP and Mail Connections
Flowintel disabled TLS certificate verification for all MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This allowed an on-path (man-in-the-middle) attacker positioned between Flowintel and its MISP or mail servers to impersonate the remote server and intercept sensitive data.
Affected connections include: - All MISP HTTPS API calls (event retrieval, attribute search, event creation, connectivity checks, and API validation) - SMTP STARTTLS connections used for sending email notifications - IMAP TLS connections used for fetching mail archives and testing connectivity
An attacker who can observe or intercept network traffic between Flowintel and the MISP or mail server could: - Capture MISP API keys and mail credentials (SMTP/IMAP passwords) - Read all threat intelligence data exchanged (events, attributes, objects, reports) - Inject or modify threat intelligence data returned to Flowintel
The vulnerability required no authentication on the part of the attacker and no user interaction; it was exploitable by any party with a network position between Flowintel and its configured MISP or mail endpoints.
Affected versions: Flowintel prior to 4.1.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.1.0
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments using Flowintel to connect to MISP over HTTPS or to mail servers through SMTP STARTTLS or IMAP TLS are exposed. The affected MISP operations include event retrieval and creation, attribute searches, connectivity checks, and API validation.
What does an attacker need to exploit it?
An attacker needs an on-path network position between Flowintel and its configured MISP or mail endpoint, allowing them to observe or intercept that traffic. No Flowintel authentication or user interaction is required.
What information or actions are at risk during exploitation?
An on-path attacker could capture MISP API keys and SMTP or IMAP credentials, read exchanged threat-intelligence data, and inject or alter threat-intelligence data returned to Flowintel. Mail traffic used for notifications, archive fetching, and connectivity testing may also be intercepted.