Skip to main content
Menu
CVEs

flowintel case existence disclosure in MISP correlation feature

CVE-2026-133843EUVD-2026-131583GHSA-63W8-Q684-42JRPublished , updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.0
Who is exposed
Not reported

Summary

flowintel has an insecure direct object reference flaw in its MISP correlation feature. A remote attacker with a low-privilege login can use it to discover the existence of cases they are not authorized to view, because the application does not check permissions on the source case or the matching cases in correlation results.

Written by a model

Original description

flowintel contains a vulnerability in the MISP correlation feature that allows unauthorized disclosure of case identifiers.

The application failed to enforce proper access controls when generating correlation lists for MISP attributes. Specifically, the system did not verify whether the requesting user had permission to view the source case or the matching cases returned in the correlation results. This lack of authorization checks allowed authenticated users to potentially discover the existence of cases they do not have access to, leading to information disclosure.

The vulnerability affects the following components:

  • Case correlation logic
  • API endpoints for retrieving correlation attributes
  • MISP object handling

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-133843 (flowintel: Insecure Direct Object Reference in MISP Correlation Feature), 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-133843 (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-133843 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133843 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/6a96e374ea1fb7cc547777ac2cd5fa98b6622da9
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-133843
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-133843"}.

Affected versions

cve.now Index

8Pof 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
  • 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

  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-133843
RecordNVD · CVE-2026-133843
Other links 1
PatchGitHub · flowintel/flowintel · Commit 6a96e374

Questions about CVE-2026-133843

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

flowintel: before 4.1.0.

Source: cve.now feed data

How do I fix CVE-2026-133843?

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.