{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-133157 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-133157 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-133157 is a medium-severity vulnerability in flowintel, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-133157 and fix it if it is affected.\n\nWhat it is: CVE-2026-133157 is a medium-severity vulnerability in flowintel, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-133157 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-133157/ (Markdown: https://insights.sbomify.com/CVE-2026-133157/index.md)","id":"CVE-2026-133157","markdown":"https://insights.sbomify.com/CVE-2026-133157/index.md","name":"CVE-2026-133157","record":{"aliases":["GHSA-m9cw-jq4w-cf5p"],"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":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"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.\n\nThe 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.\n\nPreconditions:\n- An attacker must be able to influence content that is recorded in flowintel audit logs.\n- An administrator or user must export the audit logs to CSV and open the file in a spreadsheet application that interprets formulas.\n\nSecurity impact:\n- Potential information disclosure from the spreadsheet or linked resources.\n- Potential integrity impact on data within the spreadsheet application.\n- No direct compromise of the flowintel application itself.\n\nAffected version: \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 Audit Log CSV Exports in flowintel","id":"CVE-2026-133157","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":"Harness `ToolOutputLimits` ANSI stripping can take quadratic time, blocking the event loop","id":"CVE-2026-133161"},"nickname":null,"packages":[],"prev":{"headline":"WebToffee Product Feed before 2.4.4 Authorization Bypass via Hard-coded Cron Salt","id":"CVE-2026-133117"},"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-133157/"}