External risk intelligence

Flowintel API and Mail Connections Interception Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-133648

The vulnerability involves client-side TLS certificate verification failures in Flowintel when connecting to external MISP APIs or mail servers (SMTP/IMAP). While these connections reach out to network services, Flowintel itself acts as a client or internal application rather than a public-facing edge service, gateway, or internet-accessible portal, making public internet exposure of the vulnerable component uncommon.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Flowintel related to how it handles secure connections to external services like MISP and email servers. A network attacker could potentially intercept sensitive data and credentials by impersonating these services. The main concern is confirming if your specific environment is exposed to this type of risk.

  • Unsecured connections could expose sensitive data.
  • This impacts communication with external threat intelligence and email.
  • Verify if your Flowintel setup is at risk.

Attack Path

How an attacker could exploit the issue

An attacker with network visibility between Flowintel and its external services, like MISP or mail servers, can intercept communications. By impersonating these legitimate servers, the attacker can steal sensitive credentials and data, or even alter the threat intelligence Flowintel receives. This bypasses the need for any prior access or authentication.

  • Attacker must see network traffic.
  • Vulnerable TLS verification allows impersonation.
  • Risk of credential and data theft.

Live Threat

Current exploitation, exposure, and threat context

Flowintel could expose sensitive information and credentials when connecting to MISP or mail servers due to disabled TLS certificate verification. This allows an on-path attacker to intercept data and credentials between Flowintel and its configured endpoints.

  • API keys and mail credentials at risk.
  • Intercepted network traffic can expose data.
  • Threat intelligence data could be modified.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Flowintel application owner is responsible for addressing this vulnerability, which impacts secure communication with MISP and mail servers. The first step is to identify all Flowintel deployments, confirm their exposure to the network, and determine the business criticality of the affected connections. Once ownership is confirmed, a remediation plan can be developed based on the assessed risk.

  • Application owners must address the issue.
  • Verify network exposure and business criticality.
  • Plan remediation based on confirmed risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Flowintel software used for?

Flowintel is a platform designed to manage threat intelligence by automating connections to external services. It integrates with MISP instances to retrieve and search intelligence data, and utilizes email protocols like SMTP and IMAP to send alerts or fetch information. By centralizing these communications, it helps security teams track and respond to threats efficiently.

How does CVE-2026-133648 work?

This vulnerability, classified as CWE-295 (Improper Certificate Validation), occurs because the application fails to verify the digital certificates presented by remote servers. Without this check, the software cannot confirm it is talking to a legitimate server. An attacker can exploit this by pretending to be the intended MISP or mail server, tricking Flowintel into sending sensitive data to the attacker instead.

When does this vulnerability trigger?

The flaw triggers whenever the application initiates a connection to a MISP API, or when it performs SMTP or IMAP mail operations. It is not triggered by internal software logic or local user actions; rather, it requires an attacker to be positioned on the network path between your instance and the destination server. If an attacker cannot observe or intercept that specific network traffic, they cannot perform the impersonation.

Is my Flowintel instance at risk?

According to Halo Surface Signal, this vulnerability is classified as 'Unlikely' to be exposed to the public internet because Flowintel acts as a client rather than an edge service. Your primary risk involves internal network segments where an attacker might have visibility into traffic between your Flowintel installation and its configured API or mail endpoints.

How do I start addressing this issue?

First, identify all active deployments of Flowintel within your infrastructure and document which systems they connect to for MISP or email services. Prioritize these connections based on the sensitivity of the data handled. Once you have identified these instances, consult your internal software lifecycle team to plan an update to version 4.1.0 or later, which contains the necessary security fixes for these connection protocols.

References