flowintel CSV formula injection in audit log exports
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
CSV formula injection in flowintel's audit log CSV export lets a remote attacker, without logging in, plant spreadsheet formulas in audit entries by influencing logged content, such as through captured network traffic. When an administrator or user exports the logs and opens the file in a spreadsheet application that runs formulas, those formulas can run and may expose or alter data in that spreadsheet, but the flowintel application itself is not directly compromised.
Written by a model
Original description
flowintel contains a CSV injection vulnerability in its audit log CSV export functionality. Attacker-influenced text recorded in audit logs could be interpreted as spreadsheet formulas when an administrator opened the exported CSV file in a spreadsheet application.
The vulnerable behavior allowed an attacker who could influence audit log content (for example by generating network traffic that is captured and logged) to embed formula-like strings (such as =CMD() or =HYPERLINK()) into audit entries. When the resulting CSV export was opened in a spreadsheet application, these strings could be executed as formulas, potentially leading to data exfiltration, data manipulation, or execution of further malicious actions within the spreadsheet context.
Preconditions:
- An attacker must be able to influence content that is recorded in flowintel audit logs.
- An administrator or user must export the audit logs to CSV and open the file in a spreadsheet application that interprets formulas.
Security impact:
- Potential information disclosure from the spreadsheet or linked resources.
- Potential integrity impact on data within the spreadsheet application.
- No direct compromise of the flowintel application itself.
Affected version: <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-133157 (CSV Formula Injection in Audit Log CSV 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-133157 (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-133157 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133157 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/25ad65000e62ee68a1a3444aeec73bd258189951
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-133157
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-133157"}.Affected versions
- flowintel flowintelthrough 4.0.0
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 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-133157 |
| Record | NVD · CVE-2026-133157 |
| Other links 1 | |
| Patch | GitHub · flowintel/flowintel · Commit 25ad6500 |
Questions about CVE-2026-133157
Is CVE-2026-133157 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-133157?
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.