CVE-2026-133627 — Flowintel Flowintel (4.1.0) — CWE-117
CVE-2026-133627 is a MEDIUM severity Privilege Escalation vulnerability (CWE-117) (CVSS 5.3/10) affecting Flowintel Flowintel (4.1.0). Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) with zero user interaction (UI:N), posing a direct security risk to affected deployments.
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-133627
CVSS 5.3/10 · MEDIUM · 20.11.2026
CWE: CWE-117
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
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Authentication Bypass
Summary: 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 …
Affected: flowintel:flowintel
⚡ ATTACK CHAIN
1. JWT: change alg to none, remove signature.
2. SQL bypass: ' OR '1'='1'-- in login form.
3. Direct API endpoint access without auth headers.
4. Password reset token prediction or race condition.
5. Credential stuffing with default creds.
🔧 Tools: jwt_tool, Burp Suite, Hydra, sqlmap --forms
🗺️ MITRE ATT&CK: T1078 (Valid Accounts), T1110 (Brute Force)
🌍 REAL WORLD IMPACT
🛡️ REMEDIATION
→ Apply vendor security update for flowintel:flowintel.
→ Add MFA, strengthen sessions, implement rate limiting.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]
FOFA Query