CVE-2026-133661flowintel improper authentication
CVE-2026-133661 is a improper authentication in flowintel, rated medium (5.3 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
The software does not prove who a caller is, so an attacker can pass as someone else. An action never checks whether the caller is allowed to perform it.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker act as a signed-in user, or an administrator, without valid credentials.
Is it being exploited?
There is no public report of exploitation yet. It can be exploited automatically, at scale.
What to do
- Upgrade flowintel to 4.1.0 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
FlowIntel contains multiple authorization and credential management vulnerabilities affecting connector instances, MISP helper tools, and case templates.
- Connector instance metadata, connectivity checks, and case listings accepted instance IDs without verifying if the acting user had visibility or ownership rights, allowing unauthorized access to sensitive configuration and data. - Case template serialization and creation processes exposed connector instances attached to templates regardless of the user's permissions, potentially leaking credentials or instance details to users who should not have access. - Editing connector instances allowed changes to URLs or sharing scopes without requiring re-authentication of API keys, enabling the reuse of another user's credentials in a new context or the leakage of shared keys to unauthorized endpoints. - Outbound MISP connector keys were incorrectly accepted for authenticating incoming alerts, bypassing the intended separation between outbound integration credentials and inbound alert source authentication.
These issues allow authenticated users to access unauthorized connector data, manipulate credential scopes, and potentially exploit credential confusion between different security contexts.
Affected versions: < 4.1.0
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Sign-in, session and token handling. The flaw sits between anonymous callers and authenticated sessions.
- Identity providers and SSO. The flaw sits between anonymous callers and authenticated sessions.
- Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
- Multi-tenant services. The flaw sits between one role or tenant and another.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between anonymous callers and authenticated sessions. An attacker who crosses it can act as a signed-in user, or an administrator, without valid credentials.
- Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.
Questions to answer about your own systems
- Where does flowintel run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Read more
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.