CVE-2026-133661: FlowIntel: Missing Authorization and Credential Scope Enforcement in Connector and Template Features

Published Nov 20, 2026
·
Updated

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

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.1.0
  2. Configuration

    Require users to re-enter the API key when changing a connector instance URL or sharing scope.

    FlowIntel connector instances API key re-entry when changing instance URLs or sharing scopes = required
  3. Configuration

    Use credentials distinct from outbound MISP connector keys to authenticate incoming alerts.

    FlowIntel alert ingestion alert authentication credentials = distinct from outbound MISP connector keys

Event History

Nov 20, 2026
CVE Published
via MITRE·10:57 AM
Data Sourced
via MITRE·10:57 AM
RemedyDescriptionWeakness
Data Sourced
via OSV·10:57 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Does exploitation require an existing account or user interaction?

Yes. The CVSS vector indicates that an attacker needs low-level privileges, but no user interaction is required. The issue is remotely reachable over the network.

2

Which features should be prioritized for review?

Prioritize connector instance metadata, connectivity checks, case listings, connector editing and sharing-scope changes, case template creation and serialization, and MISP helper or alert-authentication workflows. These are the areas identified as lacking authorization or credential-scope enforcement.

3

Can an attacker do more than view unauthorized connector information?

Yes. An authenticated user may be able to change connector URLs or sharing scopes without re-authenticating API keys, which can enable credential reuse in a different context or expose shared keys to unauthorized endpoints. Outbound MISP connector keys may also be accepted for incoming-alert authentication.

4

What is the assessed impact and severity?

This issue is rated medium with a CVSS score of 5.3. The vector indicates low confidentiality, integrity, and availability impact within the vulnerable component, with no indicated impact on other security authorities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203