An 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.
The vulnerability affects the case history append and merge operations. No authentication bypass or privilege escalation is required beyond normal case-management access.
Affected versions: flowintel prior to 4.1.0.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
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.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 20 Nov 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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). An 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. The vulnerability affects the case history append and merge operations. No authentication bypass or privilege escalation is required beyond normal case-management access. Affected versions: flowintel prior to 4.1.0. | |
| Title | flowintel Case History Log Injection via Line Separator Characters in User-Authored Fields | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-117 | |
| CPEs | cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flowintel
Flowintel flowintel |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-20T08:52:54.104Z
Reserved: 2026-11-20T08:52:49.070Z
Link: CVE-2026-133627
No data.
Status : Received
Published: 2026-11-20T09:20:09.587
Modified: 2026-11-20T09:20:09.587
Link: CVE-2026-133627
No data.
OpenCVE Enrichment
No data.
-
CWE-117
Improper Output Neutralization for Logs