flowintel unauthorized access in connector and template features
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.0
- Who is exposed
- Not reported
Summary
FlowIntel has several authorization flaws in its connector, MISP helper, and case template features. A logged-in user can use them to view connector data they should not see, change credential scopes, and potentially expose credentials. The flaws can be reached remotely over the network with low-privilege access and need no action from another user.
Written by a model
Original description
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 to do
Upgrade to a fixed version: 4.1.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133661 (FlowIntel: Missing Authorization and Credential Scope Enforcement in Connector and Template Features), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133661 (entry last updated 2026-11-20):
Affected:
- flowintel flowintel: fixed in 4.1.0
Fixed versions: 4.1.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133661 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133661 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/flowintel/flowintel/commit/11263af5a84f27cb342fa80343c708d44f42e840
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133661
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133661"}.Affected versions
- flowintel flowintelfixed in 4.1.0
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133661 |
| Record | NVD · CVE-2026-133661 |
| Other links 1 | |
| Patch | GitHub · flowintel/flowintel · Commit 11263af5 |
Questions about CVE-2026-133661
Is CVE-2026-133661 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133661?
flowintel: before 4.1.0.
Source: cve.now feed data
How do I fix CVE-2026-133661?
Upgrade to a fixed version: 4.1.0.
Source: cve.now feed data
Related
- CVE-2026-133663flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification
- CVE-2026-133847flowintel: Missing Authorization Check Allows Organization Admin to Edit Platform Admin Accounts via Browser Interface
- CVE-2026-133848flowintel: Organization Admin Can Delete Platform Admin Accounts Due to Missing Privilege Hierarchy Check
- CVE-2026-133854flowintel: Information Disclosure of Classification Usage via Missing Access Control
- CVE-2026-133849flowintel: Insecure Direct Object Reference in Task Calendar Access Control
- CVE-2026-133839FlowIntel Missing Authorization Check Allows Unauthorized Deletion of Evidence Files from Restricted Privileged Tasks
No corrections so far. Something wrong on this page? Report an error.