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
0.4% estimated probability of exploitation activity in the next 30 days; 37th 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-19. 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-74Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection) CWE-1236Improper Neutralization of Formula Elements in a CSV File
Show the promptExplain CVE-2026-133157 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-133157?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-133157?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-133157 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.