Skip to content
Fencer Intel
medium 4.8

CVE-2026-133178 json

CSV Formula Injection in Case and Task Exports in flowintel

published 16h ago modified 15h ago also EUVD-2026-130204

cvss
4.8
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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

Patch / fix

Is CVE-2026-133178 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
15h ago

CVSS scores

assigned by version score vector
CNA 4.0 4.8 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Affected products

  • flowintel flowintel

Classification

Weakness
  • CWE-147 Improper Neutralization of Input Terminators
  • CWE-116 Improper Encoding or Escaping of Output

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.