Skip to content
Fencer Intel
high 7.1

CVE-2026-133626 json

FlowIntel: Resource Exhaustion via Sparse CSV/JSON Table Expansion During File-to-Note Conversion

published yesterday modified yesterday also EUVD-2026-131264

cvss
7.1
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

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

Patch / fix

  • flowintel flowintel 4.1.0

Is CVE-2026-133626 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
yesterday

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-21).

CVSS scores

assigned by version score vector
CNA 4.0 7.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Affected products

  • flowintel flowintel

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.