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
0.6% estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400Uncontrolled Resource Consumption CWE-770Allocation of Resources Without Limits or Throttling
Show the promptExplain CVE-2026-133626 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-133626?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-133626?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-133626 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
googlesky/CVE-2026-1336260 stars, Python, created FlowIntel: file-to-note conversion padded every row to max columns — a sparse 1987-byte CSV expands to 274092 bytes of Markdown, exhausting…
Attack patterns (CAPEC)
CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium