{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-133178 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-133178 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-133178 is a medium-severity vulnerability in flowintel, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-133178 and fix it if it is affected.\n\nWhat it is: CVE-2026-133178 is a medium-severity vulnerability in flowintel, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-133178 in the wild and no public exploit code.\n\nAffected product: flowintel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-133178/ (Markdown: https://insights.sbomify.com/CVE-2026-133178/index.md)","id":"CVE-2026-133178","markdown":"https://insights.sbomify.com/CVE-2026-133178/index.md","name":"CVE-2026-133178","record":{"aliases":["GHSA-4c7f-gww8-5934"],"analysis":null,"analysis_generated_by":null,"assigner":"CIRCL","component":null,"cpe":[{"criteria":[{"cpe":"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*","source":"cna","version_end_including":"4.0.0"}],"n_criteria":1,"name":"Flowintel","product":"flowintel","vendor":"flowintel"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-147","name":"Improper Neutralization of Input Terminators"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"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.\n\nBecause 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.\n\nThis 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.\n\nThe vulnerability requires the victim to actively open the CSV file in a spreadsheet application; the flowintel application itself is not directly compromised.\n\nAffected: \u003c4.1.0","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"CSV Formula Injection in Case and Task Exports in flowintel","id":"CVE-2026-133178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"In JetBrains Rider before 2026.3 code execution was possible via MSBuild configuration files in parent directories","id":"CVE-2026-133179"},"nickname":null,"packages":[],"prev":{"headline":"MISP: Insufficient Authorization Allows Sync Users and External Feeds to Overwrite Organisation Details","id":"CVE-2026-133177"},"products":["flowintel"],"published":"2026-11-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","text_fixes":[],"updated":"2026-11-19","vendor_status":[],"vendors":["flowintel"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-133178/"}