GCVE-1-2026-20314 (CVE-2026-133157)
Vulnerability from gna-1 – Published: 2026-11-19 13:42 – Updated: 2026-11-19 13:42| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/25a… | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-18 14:21 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch
985a4b0d9641… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
25ad65000e62
|
fix: [security] Neutralise formulas in audit log CSV exports | 985a4b0d9641… |
Fix summary
The audit log CSV export now routes all cell values through a shared literal-text formatter (csv_safe_cell) that neutralises formula-like content by prefixing it with an apostrophe, ensuring the text is treated as inert data when opened in a spreadsheet application. Typed numeric values and JSON exports remain unaffected.
Patch summary
In app/tools/audit_logs_core.py, the rows_to_csv function was modified to import and apply csv_safe_cell from ..utils/csv_utils to every cell value before writing to the CSV writer, replacing the previous raw value pass-through. The user manual (doc/user-manual.md) was updated to explicitly state that the formula-protection behaviour also applies to audit-log CSV exports.
CVSS rationale
AV:N because the attacker-influenced content enters via network traffic captured by flowintel. AC:L because crafting a formula-like string in logged data is straightforward. AT:N because no special race or timing conditions are required. PR:N because the attacker does not need an account in flowintel to generate traffic that is logged. UI:A because an administrator must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA are N because the flowintel application itself is not compromised. SC:L and SI:L reflect the potential for a spreadsheet formula to read or modify data in the adjacent spreadsheet context. SA:N because there is no evidence of availability impact on the adjacent component.
Weakness rationale
- CWE-1236 The vulnerability allows attacker-controlled text to be written into a CSV file without neutralisation, so that spreadsheet applications interpret the text as executable formulas. This is the precise definition of formula injection.
- CWE-74 The CSV output is consumed by a downstream component (spreadsheet application) that interprets special characters (leading =, +, -, @) as formula delimiters. The product failed to neutralise these special elements before output.
Attack pattern rationale
- CAPEC-119 CAPEC-119 directly describes the technique of injecting malicious formulas or commands into CSV files that are later opened in spreadsheet applications. The patch evidence (attacker-influenced audit text becoming spreadsheet formulas in a CSV export) is a textbook instance of this attack pattern. No uncertainty in this mapping.
Assumptions to verify
- The affected version is recorded as '0' from the explicit context; no specific version range or fixed version is provided in the patch metadata.
- The assumption that the attacker can influence audit log content via network traffic is inferred from the commit message stating 'Attacker-influenced audit text'; the exact mechanism of influence is not detailed in the patch.
- CVSS impact on adjacent components (SC:L, SI:L) assumes the spreadsheet formula could read or modify data; the patch does not specify the exact capabilities of the injected formulas.
- The csv_safe_cell utility was introduced for a prior finding (F142) and is assumed to correctly neutralise all formula-triggering characters (=, +, -, @, tab, newline).
- CAPEC-119 mapping is considered high-confidence; no uncertainty noted.
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 |
- 2026-11-06 09:54 UTC Fix developed Corrective change authored (25ad65000e62ee68a1a3444aeec73bd258189951): fix: [security] Neutralise formulas in audit log CSV exports https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch
- 2026-11-18 14:20 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch
{
"containers": {
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/tools/audit_logs_core.py"
],
"product": "flowintel",
"programFiles": [
"app/tools/audit_logs_core.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 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"
}
],
"impacts": [
{
"capecId": "CAPEC-119",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-119 CSV Injection"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.1,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"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:N/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:08Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-1236",
"description": "CWE-1236 Formula Injection",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-74",
"description": "CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"orgId": "00000000-0000-4000-8000-000000000000"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951"
}
],
"solutions": [
{
"lang": "en",
"value": "The audit log CSV export now routes all cell values through a shared literal-text formatter (csv_safe_cell) that neutralises formula-like content by prefixing it with an apostrophe, ensuring the text is treated as inert data when opened in a spreadsheet application. Typed numeric values and JSON exports remain unaffected."
}
],
"title": "CSV Formula Injection in Audit Log CSV 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 is recorded as \u00270\u0027 from the explicit context; no specific version range or fixed version is provided in the patch metadata.",
"The assumption that the attacker can influence audit log content via network traffic is inferred from the commit message stating \u0027Attacker-influenced audit text\u0027; the exact mechanism of influence is not detailed in the patch.",
"CVSS impact on adjacent components (SC:L, SI:L) assumes the spreadsheet formula could read or modify data; the patch does not specify the exact capabilities of the injected formulas.",
"The csv_safe_cell utility was introduced for a prior finding (F142) and is assumed to correctly neutralise all formula-triggering characters (=, +, -, @, tab, newline).",
"CAPEC-119 mapping is considered high-confidence; no uncertainty noted."
],
"capecRationale": [
{
"capecId": "CAPEC-119",
"rationale": "CAPEC-119 directly describes the technique of injecting malicious formulas or commands into CSV files that are later opened in spreadsheet applications. The patch evidence (attacker-influenced audit text becoming spreadsheet formulas in a CSV export) is a textbook instance of this attack pattern. No uncertainty in this mapping."
}
],
"commit": "25ad65000e62ee68a1a3444aeec73bd258189951",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N because the attacker-influenced content enters via network traffic captured by flowintel. AC:L because crafting a formula-like string in logged data is straightforward. AT:N because no special race or timing conditions are required. PR:N because the attacker does not need an account in flowintel to generate traffic that is logged. UI:A because an administrator must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA are N because the flowintel application itself is not compromised. SC:L and SI:L reflect the potential for a spreadsheet formula to read or modify data in the adjacent spreadsheet context. SA:N because there is no evidence of availability impact on the adjacent component.",
"fixSummary": "The audit log CSV export now routes all cell values through a shared literal-text formatter (csv_safe_cell) that neutralises formula-like content by prefixing it with an apostrophe, ensuring the text is treated as inert data when opened in a spreadsheet application. Typed numeric values and JSON exports remain unaffected.",
"generatedAt": "2026-11-18T14:21:08.189351Z",
"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": "985a4b0d9641681ef352721b0b961fbf7910ea60989bc6e6d422ca72ea285a6c",
"patchSummary": "In app/tools/audit_logs_core.py, the rows_to_csv function was modified to import and apply csv_safe_cell from ..utils/csv_utils to every cell value before writing to the CSV writer, replacing the previous raw value pass-through. The user manual (doc/user-manual.md) was updated to explicitly state that the formula-protection behaviour also applies to audit-log CSV exports.",
"patchTruncated": false,
"patches": [
{
"commit": "25ad65000e62ee68a1a3444aeec73bd258189951",
"date": "Fri, 6 Nov 2026 10:54:28 +0100",
"patchSha256": "985a4b0d9641681ef352721b0b961fbf7910ea60989bc6e6d422ca72ea285a6c",
"retrievedAt": "2026-11-18T14:20:43.501372Z",
"source": "https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch",
"subject": "fix: [security] Neutralise formulas in audit log CSV exports"
}
],
"source": "https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:21:08Z",
"version": "2.0.3"
},
"subject": "fix: [security] Neutralise formulas in audit log CSV exports",
"weaknessRationale": [
{
"cweId": "CWE-1236",
"rationale": "The vulnerability allows attacker-controlled text to be written into a CSV file without neutralisation, so that spreadsheet applications interpret the text as executable formulas. This is the precise definition of formula injection."
},
{
"cweId": "CWE-74",
"rationale": "The CSV output is consumed by a downstream component (spreadsheet application) that interprets special characters (leading =, +, -, @) as formula delimiters. The product failed to neutralise these special elements before output."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (25ad65000e62ee68a1a3444aeec73bd258189951): fix: [security] Neutralise formulas in audit log CSV exports",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch"
],
"timestamp": "2026-11-06T09:54:28Z",
"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/25ad65000e62ee68a1a3444aeec73bd258189951.patch"
],
"timestamp": "2026-11-18T14:20:43.501372Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20314"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "00000000-0000-4000-8000-000000000000",
"cveId": "CVE-2026-133157",
"datePublished": "2026-11-19T13:42:04.260146Z",
"dateReserved": "2026-11-19T13:42:50.926Z",
"dateUpdated": "2026-11-19T13:42:51.950405Z",
"state": "PUBLISHED",
"vulnId": "gcve-1-2026-20314"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Solutions
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.
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
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.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.