flowintel formula injection in case and task CSV exports
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
flowintel's case and task CSV exports write user-supplied field values without neutralising them, so a remote attacker with editor-level access can store text that a spreadsheet runs as a live formula when a victim opens the exported file in Microsoft Excel or LibreOffice Calc. This can lead to unintended data changes within the spreadsheet, possible data exfiltration through formula functions, or downstream command execution, depending on the spreadsheet application's configuration.
Written by a model
Original description
flowintel allows users with editor-level access to author case and task fields, including aggregated tags. When these records are exported as CSV, the field values are written verbatim into the output file.
Because no sanitisation is applied to user-supplied text before CSV serialisation, an attacker can store values that begin with spreadsheet formula triggers (such as =, +, -, @, or their fullwidth Unicode equivalents, or leading control/whitespace characters). When a victim opens the exported CSV in a spreadsheet application (e.g. Microsoft Excel, LibreOffice Calc), the stored text is interpreted and executed as a live formula rather than displayed as literal text.
This can lead to unintended data manipulation within the spreadsheet, potential data exfiltration via formula functions, or execution of downstream commands depending on the spreadsheet application and its configuration.
The vulnerability requires the victim to actively open the CSV file in a spreadsheet application; the flowintel application itself is not directly compromised.
Affected: <4.1.0
What to do
Apply the patch listed under Evidence.
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-133178 (CSV Formula Injection in Case and Task Exports in flowintel), 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-133178 (entry last updated 2026-11-19):
Affected:
- flowintel flowintel: through 4.0.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133178 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133178 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/adef89f5c82729da7bdf1c25b32ba8660b8376d5
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-133178
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-133178"}.Affected versions
- flowintel flowintelthrough 4.0.0
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- 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
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133178 |
| Record | NVD · CVE-2026-133178 |
| Other links 1 | |
| Patch | GitHub · flowintel/flowintel · Commit adef89f5 |
Questions about CVE-2026-133178
Is CVE-2026-133178 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-133178?
flowintel: through 4.0.0.
Source: cve.now feed data
Related
- CVE-2026-81826Flowintel Fails to Invalidate Active Sessions After Password Change
- CVE-2026-81818Flowintel Organization Administrator Can Reset Full Administrator Password and Escalate Privileges
- CVE-2026-81662Flowintel Alert Settings Configuration Allows Remote Code Execution via Arbitrary Configuration Keys
- CVE-2026-81743Flowintel Arbitrary Log File Path Allows Remote Code Execution via Template Injection
- CVE-2026-124850SQL Injection in Database Migration via Stored Connector Identifiers in flowintel
- CVE-2026-81817Flowintel Missing Task-to-Case Authorization Allows Cross-Case Task Modification
No corrections so far. Something wrong on this page? Report an error.