{"api_version":"1","generated_at":"2026-11-20T18:44:08+00:00","cve":"CVE-2026-133627","urls":{"html":"https://cve.report/CVE-2026-133627","api":"https://cve.report/api/cve/CVE-2026-133627.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-133627","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-133627"},"summary":{"title":"flowintel Case History Log Injection via Line Separator Characters in User-Authored Fields","description":"flowintel contains a log injection vulnerability in its case history (audit log) subsystem. The case history is stored as a line-delimited file where each line represents a single event attributed to a specific user. User-controlled fields, including user names, event messages, and case titles used during case merging, were written to the history file without sanitizing embedded line separator characters (such as carriage return, line feed, vertical tab, form feed, and Unicode line/paragraph separators).\n\nAn authenticated user with the ability to create or modify case history entries could embed line separators in these fields. Upon writing, the injected separators would split a single intended entry into multiple lines, each of which the history format interprets as a distinct event. This allows an attacker to forge additional history entries attributed to arbitrary users, corrupting the audit trail and undermining the integrity of case records.\n\nThe vulnerability affects the case history append and merge operations. No authentication bypass or privilege escalation is required beyond normal case-management access.\n\nAffected versions: flowintel prior to 4.1.0.","state":"PUBLISHED","assigner":"CIRCL","published_at":"2026-11-20 09:20:09","updated_at":"2026-11-20 09:20:09"},"problem_types":["CWE-117","CWE-117 CWE-117 Improper Output Neutralization for Logs"],"metrics":[{"version":"4.0","source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","score":"5.3","severity":"MEDIUM","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","data":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","baseScore":5.3,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"LOW","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"version":"4.0","source":"CNA","type":"CVSS","score":"5.3","severity":"MEDIUM","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","data":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":5.3,"baseSeverity":"MEDIUM","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"LOW","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/flowintel/flowintel/commit/842a948507b87ee8c614ba2871ffecb3172d29e1","name":"https://github.com/flowintel/flowintel/commit/842a948507b87ee8c614ba2871ffecb3172d29e1","refsource":"5a6e4751-2f3f-4070-9419-94fb35b644e8","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-133627","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-133627","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"flowintel","product":"flowintel","version":"affected 4.1.0 semver","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"The fix introduces a sanitization helper that replaces all splitlines()-recognized line separator characters (CR, LF, VT, FF, file/group/record separators, NEL, Unicode line and paragraph separators) with a single space before any user-authored content is written to the case history file. The helper is applied to the author name, the event message, and the case title during merge operations, ensuring each history entry remains on exactly one line and cannot be split into forged entries.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"elhoim","lang":"en"},{"source":"CNA","value":"David Cruciani","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"cpes":["cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"],"modules":["app/case/common_core.py"],"product":"flowintel","programFiles":["app/case/common_core.py"],"repo":"https://github.com/flowintel/flowintel","vendor":"flowintel","versions":[{"lessThan":"4.1.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 log injection vulnerability in its case history (audit log) subsystem. The case history is stored as a line-delimited file where each line represents a single event attributed to a specific user. User-controlled fields, including user names, event messages, and case titles used during case merging, were written to the history file without sanitizing embedded line separator characters (such as carriage return, line feed, vertical tab, form feed, and Unicode line/paragraph separators).\n\nAn authenticated user with the ability to create or modify case history entries could embed line separators in these fields. Upon writing, the injected separators would split a single intended entry into multiple lines, each of which the history format interprets as a distinct event. This allows an attacker to forge additional history entries attributed to arbitrary users, corrupting the audit trail and undermining the integrity of case records.\n\nThe vulnerability affects the case history append and merge operations. No authentication bypass or privilege escalation is required beyond normal case-management access.\n\nAffected versions: flowintel prior to 4.1.0."}],"impacts":[{"capecId":"CAPEC-66","descriptions":[{"lang":"en","value":"CAPEC-66 HTTP Request/Response Splitting"}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":5.3,"baseSeverity":"MEDIUM","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"LOW","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-20T08:42:41Z","version":"2.0.3"},"type":"SSVC"},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-117","description":"CWE-117 Improper Output Neutralization for Logs","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-20T08:52:54.104Z","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","shortName":"CIRCL"},"references":[{"name":"Security patch","tags":["patch"],"url":"https://github.com/flowintel/flowintel/commit/842a948507b87ee8c614ba2871ffecb3172d29e1"}],"solutions":[{"lang":"en","value":"The fix introduces a sanitization helper that replaces all splitlines()-recognized line separator characters (CR, LF, VT, FF, file/group/record separators, NEL, Unicode line and paragraph separators) with a single space before any user-authored content is written to the case history file. The helper is applied to the author name, the event message, and the case title during merge operations, ensuring each history entry remains on exactly one line and cannot be split into forged entries."}],"title":"flowintel Case History Log Injection via Line Separator Characters in User-Authored Fields","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":["PR:L assumes the attacker needs at least basic authenticated access to the case management interface to submit history entries; the patch does not specify whether unauthenticated access is possible.","VI:L assumes the integrity impact is limited to the case history file and does not extend to other system components or databases; the patch only modifies the file-writing path.","CAPEC-66 is the closest available pattern for structured-output injection via line separators; no CAPEC specifically covers log-file injection, so this mapping carries some uncertainty.","The affected version range (0 to <4.1.0) is taken from the explicit analyst context; the patch itself does not encode version boundaries.","The commit message references an internal finding identifier (F124 / G29) which is not publicly resolvable and is not included as a reference."],"capecRationale":[{"capecId":"CAPEC-66","rationale":"CAPEC-66 describes the technique of injecting CRLF or line separator characters into structured output to create additional entries or split a single record into multiple. The underlying mechanism here is identical: an attacker embeds line separators in user input to split a single log entry into multiple forged entries. The context differs (log file rather than HTTP response), but no CAPEC pattern more precisely captures structured-output injection via line separators. This is the closest available match."}],"commit":"842a948507b87ee8c614ba2871ffecb3172d29e1","confidence":"medium","credits":[{"lang":"en","type":"reporter","value":"elhoim"},{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"cvssRationale":"AV:N: The application is a web-based case management tool; input is submitted over the network. AC:L: Exploitation requires only embedding a newline character in a name, message, or title field; no race conditions or special timing. AT:N: No special attack conditions are needed. PR:L: The attacker must be an authenticated user with access to create or modify case history entries. UI:N: No victim interaction is required beyond the attacker's own submission. VC:N: No confidentiality impact; the vulnerability does not expose data. VI:L: Integrity impact is limited to forging entries in a single case's history file; it does not compromise the broader system or other cases. VA:N: No availability impact. SC/SI/SA:N: The impact is confined to the application's own log file and does not cross a security scope boundary.","fixSummary":"The fix introduces a sanitization helper that replaces all splitlines()-recognized line separator characters (CR, LF, VT, FF, file/group/record separators, NEL, Unicode line and paragraph separators) with a single space before any user-authored content is written to the case history file. The helper is applied to the author name, the event message, and the case title during merge operations, ensuring each history entry remains on exactly one line and cannot be split into forged entries.","generatedAt":"2026-11-20T08:42:41.961994Z","generator":"patch2vuln.py","model":"qwen3.8:27b","modelComparison":{"potentialErrors":[],"rankings":[{"agreementScore":11,"assumptionCount":5,"confidence":"medium","model":"qwen3.8:27b","score":7}],"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":"eab799b16980a28458755cce56ea9897af43b9a630aec94b557deb9c8f373ab4","patchSummary":"In app/case/common_core.py, a compiled regex _HISTORY_LINE_BREAKS matching all splitlines() separators is added, along with a helper function _history_one_line() that substitutes matches with a space. In save_history(), the author name and message are passed through _history_one_line() before being written. In append_history_file(), each source line and the merging case title are also sanitized via _history_one_line() before being appended to the destination history file, and an explicit newline is written to terminate each merged entry.","patchTruncated":false,"patches":[{"commit":"842a948507b87ee8c614ba2871ffecb3172d29e1","date":"Fri, 6 Nov 2026 10:54:12 +0100","patchSha256":"eab799b16980a28458755cce56ea9897af43b9a630aec94b557deb9c8f373ab4","retrievedAt":"2026-11-20T08:41:59.334828Z","source":"https://github.com/flowintel/flowintel/commit/842a948507b87ee8c614ba2871ffecb3172d29e1.patch","sourceUrl":"https://github.com/flowintel/flowintel/commit/842a948507b87ee8c614ba2871ffecb3172d29e1.patch","subject":"fix: [security] Keep case history entries on a single line"}],"source":"https://github.com/flowintel/flowintel/commit/842a948507b87ee8c614ba2871ffecb3172d29e1.patch","ssvc":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"Supplier","timestamp":"2026-11-20T08:42:41Z","version":"2.0.3"},"subject":"fix: [security] Keep case history entries on a single line","weaknessRationale":[{"cweId":"CWE-117","rationale":"User-controlled data (names, messages, titles) is written to a structured log file without neutralizing line separator characters, allowing injection of additional log entries. This is the textbook definition of CWE-117."}]}},"bcp-05-x-03":{"x_timeline":{"events":[{"description":"Corrective change authored (842a948507b87ee8c614ba2871ffecb3172d29e1): fix: [security] Keep case history entries on a single line","id":"evt-fix-developed-1","references":["https://github.com/flowintel/flowintel/commit/842a948507b87ee8c614ba2871ffecb3172d29e1.patch"],"timestamp":"2026-11-06T09:54:12Z","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/842a948507b87ee8c614ba2871ffecb3172d29e1.patch"],"timestamp":"2026-11-20T08:41:59.334828Z","type":"fix-available"}]}}},"recordType":"advisory","vulnId":"GCVE-1-2026-20212"}]}},"cveMetadata":{"assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","assignerShortName":"CIRCL","cveId":"CVE-2026-133627","datePublished":"2026-11-20T08:52:54.104Z","dateReserved":"2026-11-20T08:52:49.070Z","dateUpdated":"2026-11-20T08:52:54.104Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 09:20:09","lastModifiedDate":"2026-11-20 09:20:09","problem_types":["CWE-117","CWE-117 CWE-117 Improper Output Neutralization for Logs"],"metrics":{"cvssMetricV40":[{"source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","cvssData":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","baseScore":5.3,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"LOW","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}}],"ssvcV203":[{"source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","ssvcData":{"timestamp":"2026-11-20T08:42:41Z","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"role":"Supplier","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"133627","Ordinal":"1","Title":"flowintel Case History Log Injection via Line Separator Characte","CVE":"CVE-2026-133627","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"133627","Ordinal":"1","NoteData":"flowintel contains a log injection vulnerability in its case history (audit log) subsystem. The case history is stored as a line-delimited file where each line represents a single event attributed to a specific user. User-controlled fields, including user names, event messages, and case titles used during case merging, were written to the history file without sanitizing embedded line separator characters (such as carriage return, line feed, vertical tab, form feed, and Unicode line/paragraph separators).\n\nAn authenticated user with the ability to create or modify case history entries could embed line separators in these fields. Upon writing, the injected separators would split a single intended entry into multiple lines, each of which the history format interprets as a distinct event. This allows an attacker to forge additional history entries attributed to arbitrary users, corrupting the audit trail and undermining the integrity of case records.\n\nThe vulnerability affects the case history append and merge operations. No authentication bypass or privilege escalation is required beyond normal case-management access.\n\nAffected versions: flowintel prior to 4.1.0.","Type":"Description","Title":"flowintel Case History Log Injection via Line Separator Characte"}]}}}