Skip to main content
Menu
CVEs

flowintel unauthorized reads and writes via IDOR in Analyzer

CVE-2026-133662EUVD-2026-131457GHSA-65WF-XJF6-M9M4Published , updated

8.4HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.0
Who is exposed
Not reported

Summary

A flaw in the flowintel Analyzer feature lets an attacker reach the web interface or REST API over the network with a low-privilege login. From there, the attacker can read other users' stored analyzer results by UUID and write notes, tasks, and MISP objects or attributes into another organization's case.

Written by a model

Original description

flowintel contains multiple authorization bypass vulnerabilities in its Analyzer (MISP Modules) functionality, affecting both the web interface and the REST API.

  • Saving analyzer results to a case or task accepted caller-supplied case and task identifiers without verifying that the authenticated user is a member of the target case or holds the required restricted-task permissions. An authenticated user could write notes, create tasks, and attach MISP objects or attributes into another organization's case.
  • Stored analyzer results were retrievable by UUID by any authenticated user. Both the web endpoint and the API endpoint returned the full result payload without checking ownership, exposing another user's analysis output.
  • The save handler did not validate the structure of the request, did not reject conflicting destination selections, and did not halt processing when a task-note operation failed, allowing partial or unintended writes.

Preconditions: the attacker must possess a valid authenticated session (or API token) in flowintel. No administrative role is required.

Security impact: unauthorized cross-tenant data disclosure (analyzer results) and unauthorized cross-tenant data modification (notes, tasks, MISP objects/attributes in another organization's case).

Affected versions: flowintel prior to 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-133662 (flowintel Analyzer: Missing Authorization on Result Reads and Case/Task Writes (IDOR)), 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-133662 (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-133662 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133662 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/90e2845cf6239ed38962ce96c3003881f73c713e
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-133662
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-133662"}.

Affected versions

cve.now Index

11Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.4/10CVSS 8.4
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133662
RecordNVD · CVE-2026-133662
Other links 1
PatchGitHub · flowintel/flowintel · Commit 90e2845c

Questions about CVE-2026-133662

Is CVE-2026-133662 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-133662?

flowintel: before 4.1.0.

Source: cve.now feed data

How do I fix CVE-2026-133662?

Upgrade to a fixed version: 4.1.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.