PoC Monitor
← All CVEs
CVE-2026-133626published 20 Nov 2026 08:52 UTCData: JSON · API

FlowIntel

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

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

First public PoC 8 hafter publication · 20 Nov 2026
Public PoCs11 on GitHub
CVSS7.1high · scored by CNA · CWE-400
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

flowintel flowintel
  • < 4.1.0

Fixed in 4.1.0

Mitigation

The fix introduces bounds on table expansion: a maximum padded-cell count (50,000) and a maximum padding ratio (4x filled cells). When a CSV or JSON dataset would exceed these limits, the original content is preserved in a safely fenced code block instead of being rendered as a table. Additionally, nested JSON values in table cells are now serialized in compact form (no indentation), and the JSON fallback path uses the same safe fencing helper, preventing both quadratic cell expansion and indentation-based output inflation.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published20 Nov 2026 · t = 0First public PoC20 Nov 2026 · t+8h

First public PoC 8 h after publication; not in CISA KEV. First PoC: googlesky/CVE-2026-133626 (created 20 Nov 2026, found by us: 20 Nov 2026).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedFound by usStarsAssessment
googlesky/CVE-2026-133626 20 Nov 2026 +8 h 20 Nov 2026 0 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.