CVE-2026-133627: flowintel Case History Log Injection via Line Separator Characters in User-Authored Fields

Published Nov 20, 2026
·
Updated

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.

Affected Software

1 affected component
FlowIntel FlowIntel<4.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade flowintel to a version that resolves this vulnerability.

    Fixed in 4.1.0

Event History

Nov 20, 2026
CVE Published
via MITRE·08:52 AM
Data Sourced
via MITRE·08:52 AM
RemedyDescriptionWeakness
Data Sourced
via OSV·08:52 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:20 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated user with normal case-management access who can create or modify case history entries can exploit it. No authentication bypass or privilege escalation is needed.

2

Which operations are affected?

The affected paths are case history append operations and case merge operations, including user-controlled names, event messages, and case titles used during merging.

3

What could an attacker do?

By embedding line separator characters in controlled fields, an attacker can cause one history entry to be parsed as multiple entries. The injected entries can be forged as though they were attributed to arbitrary users, compromising audit-trail integrity.

4

Which versions need remediation?

flowintel versions earlier than 4.1.0 are affected. Upgrading to 4.1.0 or later addresses the stated affected-version range.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203