Threat Feed

CVE-2026-133648: Flowintel Disables TLS Certificate Verification for MISP and Mail Connections

Exploitation: None known · CVSS 9.9 Critical · Unauthenticated · Published 2026-11-20

Description

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.

Enclave's analysis

Flowintel turned off TLS certificate checking on every outbound connection it makes to MISP and to its configured mail servers (SMTP/IMAP). An attacker sitting on the network path between Flowintel and those endpoints can impersonate them, steal MISP API keys and mail credentials, and read or tamper with threat-intel data flowing through — no login or click needed once that position exists. There's no public exploit and no sign of in-the-wild abuse; it was fixed in 4.1.0 after private disclosure. Upgrade, and check whether your MISP/mail traffic actually crosses a network someone could intercept.

Fix

Upgrade flowintel/flowintel to 4.1.0. No fixed version is listed for flowintel; follow the vendor advisory.

Vendor advisory

Affected versions

ProductVulnerableFixed in
flowintel0 before 4.1.0Not listed
flowintel/flowintel< 4.1.04.1.0

Seen in 2 sources