GCVE-1-2026-20316 (CVE-2026-133178)

Vulnerability from gna-1 – Published: 2026-11-19 14:11 – Updated: 2026-11-19 14:11
VLAI
Title
CSV Formula Injection in Case and Task Exports in flowintel
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
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CNA (v2.0.3)
Decision recorded 2026-11-18 14:21 UTC
CWE
  • CWE-147 - Improper Neutralization of Input with Special Element Used for a Spreadsheet (CSV and DSL)
  • CWE-116 - Improper Encoding or Escaping of Output
Assigner
CIRCL GNA GNA-1
GNA scorecard A 91/100 over 279 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
flowintel flowintel Affected: 0 , ≤ 4.0.0 (semver)
    cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Human-reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-18 14:21
Model
qwen3.8:27b
Input
https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch 5c27997cbe9f…
Confidence
high
Commit Subject Patch SHA-256
adef89f5c827 fix: [security] Neutralise formulas in case and task CSV 5c27997cbe9f…
Fix summary

A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings—those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters—and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged.

Patch summary

New file app/utils/csv_utils.py defines csv_safe_cell(value) which returns an empty string for None, prepends an apostrophe to strings that start with tab/CR/LF or whose lstrip()-ed form begins with =, +, -, @, or fullwidth equivalents (=, +, -, @), and otherwise returns the value unchanged. In app/tools/tools.py the _cases_to_csv function is modified so that both case rows and task rows are wrapped with a dict comprehension applying csv_safe_cell to every field before writer.writerow. The user manual (doc/user-manual.md) gains a note explaining the apostrophe-prefixing behaviour and that JSON exports preserve original text.

CVSS rationale

AV:N – exploitation occurs over the network via the web interface. AC:L – crafting formula-like text requires no special conditions. AT:N – no specific attack prerequisites. PR:L – the attacker needs editor-level access to create or modify case/task fields. UI:A – the victim must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA:N – the primary system (flowintel) suffers no direct confidentiality, integrity, or availability impact. SC:L – the secondary system (spreadsheet) may leak data via formula functions. SI:L – the secondary system's data integrity can be altered by injected formulas. SA:N – no availability impact on the secondary system.

Weakness rationale
  • CWE-147 The patch directly addresses the case where user-controlled text is written into a CSV file without neutralising spreadsheet formula triggers (=, +, -, @, fullwidth variants, control characters). This is the exact definition of CWE-147.
  • CWE-116 More broadly, the CSV output encoding did not escape or neutralise special characters that carry meaning in the downstream consumer (spreadsheet application), fitting the general CWE-116 category.
Attack pattern rationale
  • CAPEC-117 The patch neutralises spreadsheet formula injection via CSV export, which is the canonical CSV Injection attack pattern. An attacker stores formula-like text in application fields; when the CSV is opened in a spreadsheet, the formula executes. CAPEC-117 is the most specific and directly applicable pattern. Confidence is high because the commit message, code changes, and documentation all explicitly reference spreadsheet formula neutralisation in CSV output.
Assumptions to verify
  • The affected version range is not explicitly stated in the patch; the metadata field 'affected_version' contains the placeholder value '0'. All versions prior to commit adef89f5 are assumed affected.
  • PR:L assumes the attacker needs at least editor-level access to create or modify case/task fields, based on the editor_required decorator visible in the surrounding code. If the application allows unauthenticated case creation, PR would be N.
  • The CVSS secondary-scope impact (SC:L, SI:L) assumes the victim's spreadsheet application executes injected formulas; actual impact depends on the specific application and its security settings.
  • CAPEC-117 (CSV Injection) is selected as the closest match; if this CAPEC ID is not present in the target CAPEC version, CAPEC-66 (Leverage Executable Code) would be the next-best alternative.
  • The fullwidth Unicode formula triggers (=, +, -, @) are included in the fix, suggesting the developers considered non-ASCII bypass vectors; the CVSS does not separately account for this as it does not change the base score.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 8 11 high 5
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-06 09:54 UTC Fix developed Corrective change authored (adef89f5c82729da7bdf1c25b32ba8660b8376d5): fix: [security] Neutralise formulas in case and task CSV https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch
  2. 2026-11-18 14:21 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch

{
  "containers": {
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "app/tools/tools.py (_cases_to_csv)",
            "app/utils/csv_utils.py (new)"
          ],
          "product": "flowintel",
          "programFiles": [
            "app/tools/tools.py",
            "app/utils/csv_utils.py"
          ],
          "repo": "https://github.com/flowintel/flowintel",
          "vendor": "flowintel",
          "versions": [
            {
              "lessThanOrEqual": "4.0.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "elhoim"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "David Cruciani"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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"
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-117",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-117 CSV Injection"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 4.8,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "LOW",
            "subIntegrityImpact": "LOW",
            "userInteraction": "ACTIVE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "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",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "partial"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-18T14:21:36Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-147",
              "description": "CWE-147 Improper Neutralization of Input with Special Element Used for a Spreadsheet (CSV and DSL)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-116",
              "description": "CWE-116 Improper Encoding or Escaping of Output",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "orgId": "00000000-0000-4000-8000-000000000000"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings\u2014those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters\u2014and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged."
        }
      ],
      "title": "CSV Formula Injection in Case and Task Exports in flowintel",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "full",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The affected version range is not explicitly stated in the patch; the metadata field \u0027affected_version\u0027 contains the placeholder value \u00270\u0027. All versions prior to commit adef89f5 are assumed affected.",
                  "PR:L assumes the attacker needs at least editor-level access to create or modify case/task fields, based on the editor_required decorator visible in the surrounding code. If the application allows unauthenticated case creation, PR would be N.",
                  "The CVSS secondary-scope impact (SC:L, SI:L) assumes the victim\u0027s spreadsheet application executes injected formulas; actual impact depends on the specific application and its security settings.",
                  "CAPEC-117 (CSV Injection) is selected as the closest match; if this CAPEC ID is not present in the target CAPEC version, CAPEC-66 (Leverage Executable Code) would be the next-best alternative.",
                  "The fullwidth Unicode formula triggers (\uff1d, \uff0b, \uff0d, \uff20) are included in the fix, suggesting the developers considered non-ASCII bypass vectors; the CVSS does not separately account for this as it does not change the base score."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-117",
                    "rationale": "The patch neutralises spreadsheet formula injection via CSV export, which is the canonical CSV Injection attack pattern. An attacker stores formula-like text in application fields; when the CSV is opened in a spreadsheet, the formula executes. CAPEC-117 is the most specific and directly applicable pattern. Confidence is high because the commit message, code changes, and documentation all explicitly reference spreadsheet formula neutralisation in CSV output."
                  }
                ],
                "commit": "adef89f5c82729da7bdf1c25b32ba8660b8376d5",
                "confidence": "high",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "elhoim"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "David Cruciani"
                  }
                ],
                "cvssRationale": "AV:N \u2013 exploitation occurs over the network via the web interface. AC:L \u2013 crafting formula-like text requires no special conditions. AT:N \u2013 no specific attack prerequisites. PR:L \u2013 the attacker needs editor-level access to create or modify case/task fields. UI:A \u2013 the victim must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA:N \u2013 the primary system (flowintel) suffers no direct confidentiality, integrity, or availability impact. SC:L \u2013 the secondary system (spreadsheet) may leak data via formula functions. SI:L \u2013 the secondary system\u0027s data integrity can be altered by injected formulas. SA:N \u2013 no availability impact on the secondary system.",
                "fixSummary": "A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings\u2014those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters\u2014and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged.",
                "generatedAt": "2026-11-18T14:21:36.786654Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 5,
                      "confidence": "high",
                      "model": "qwen3.8:27b",
                      "score": 8
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "5c27997cbe9fc0f551792f71c7bdae7d1eeaa6b849afcc78c0a6cf8af12dcf06",
                "patchSummary": "New file app/utils/csv_utils.py defines csv_safe_cell(value) which returns an empty string for None, prepends an apostrophe to strings that start with tab/CR/LF or whose lstrip()-ed form begins with =, +, -, @, or fullwidth equivalents (\uff1d, \uff0b, \uff0d, \uff20), and otherwise returns the value unchanged. In app/tools/tools.py the _cases_to_csv function is modified so that both case rows and task rows are wrapped with a dict comprehension applying csv_safe_cell to every field before writer.writerow. The user manual (doc/user-manual.md) gains a note explaining the apostrophe-prefixing behaviour and that JSON exports preserve original text.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "adef89f5c82729da7bdf1c25b32ba8660b8376d5",
                    "date": "Fri, 6 Nov 2026 10:54:23 +0100",
                    "patchSha256": "5c27997cbe9fc0f551792f71c7bdae7d1eeaa6b849afcc78c0a6cf8af12dcf06",
                    "retrievedAt": "2026-11-18T14:21:08.763444Z",
                    "source": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
                    "sourceUrl": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
                    "subject": "fix: [security] Neutralise formulas in case and task CSV"
                  }
                ],
                "source": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-18T14:21:36Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Neutralise formulas in case and task CSV",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-147",
                    "rationale": "The patch directly addresses the case where user-controlled text is written into a CSV file without neutralising spreadsheet formula triggers (=, +, -, @, fullwidth variants, control characters). This is the exact definition of CWE-147."
                  },
                  {
                    "cweId": "CWE-116",
                    "rationale": "More broadly, the CSV output encoding did not escape or neutralise special characters that carry meaning in the downstream consumer (spreadsheet application), fitting the general CWE-116 category."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (adef89f5c82729da7bdf1c25b32ba8660b8376d5): fix: [security] Neutralise formulas in case and task CSV",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch"
                    ],
                    "timestamp": "2026-11-06T09:54:23Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch"
                    ],
                    "timestamp": "2026-11-18T14:21:08.763444Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "gcve-1-2026-20316"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "00000000-0000-4000-8000-000000000000",
    "cveId": "CVE-2026-133178",
    "datePublished": "2026-11-19T14:11:46.797634Z",
    "dateReserved": "2026-11-19T14:11:54.087Z",
    "dateUpdated": "2026-11-19T14:11:54.259320Z",
    "state": "PUBLISHED",
    "vulnId": "gcve-1-2026-20316"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Solutions

CNA
A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings—those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters—and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged.

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.