Skip to main content
Menu
CVEs

flowintel denial of service in file-to-note conversion

CVE-2026-133626EUVD-2026-131264GHSA-37MF-JX94-7VMRPublished , updated

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

Summary

FlowIntel is affected by a resource exhaustion flaw in its file-to-note conversion feature, where converting a crafted CSV or JSON file into a case note can exhaust a worker process's memory or CPU. An attacker with a low-privilege account who can access a case can trigger it remotely by attaching and converting such a file, which can disrupt service for other users.

Written by a model

Original description

FlowIntel contains a resource exhaustion vulnerability in its file-to-note conversion feature. When a user converts an attached CSV or JSON file into a case note, the application renders the data as a Markdown table by padding every row to the maximum column count. A crafted file with a small number of filled cells but a very large number of columns (or keys) causes the application to allocate a quadratic number of padded table cells, potentially exhausting a worker process in memory or CPU.

The same issue affects nested JSON values rendered inside table cells, where pretty-printed indentation further inflates the output size.

Preconditions:

  • An authenticated user with access to a case in FlowIntel
  • Ability to attach and convert a CSV or JSON file to a note

Impact:

  • Denial of service: exhaustion of a worker process, potentially disrupting service for other users
  • No confidentiality or integrity impact

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-133626 (FlowIntel: Resource Exhaustion via Sparse CSV/JSON Table Expansion During File-to-Note Conversion), 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-133626 (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-133626 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133626 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/90b822a0fca35d33688730772b964b478c7fcde6
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-133626
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-133626"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

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

Questions about CVE-2026-133626

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

flowintel: before 4.1.0.

Source: cve.now feed data

How do I fix CVE-2026-133626?

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.