Flowintel
Monthly
Persistent session hijacking is possible in Flowintel version 3.3.0 and later because the application fails to invalidate existing authenticated sessions when a user changes their password. An attacker who already holds a valid session token (from prior access or theft) keeps full authenticated access to the account even after the victim resets the password, since the old session remains usable until natural expiry. No public exploit has been identified at time of analysis, and the issue is not in CISA KEV; a vendor fix commit exists.
Privilege escalation in Flowintel's administrative user-edit API allows an organization administrator to modify full administrator accounts within their own organization, including resetting passwords, effectively enabling account takeover of a higher-privileged identity. Affected versions are 3.3.0 and above, as confirmed by upstream commit ffe64d1133b7d84909a69661bd5fee607e9ce757 which adds the missing role-hierarchy boundary check. No public exploit has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Broken object-level authorization across Flowintel task endpoints allows authenticated editor-level users to perform unauthorized operations on tasks belonging to cases they do not own. Flowintel versions >= 3.3.0 accept a case ID and task ID pair on task-related routes but previously failed to verify that the referenced task actually belonged to the supplied case, enabling cross-case data access and manipulation. No public exploit or CISA KEV listing exists at time of analysis, but the CVSS 4.0 score of 7.2 reflects high integrity impact - affected operations include task editing, deletion, note management, file handling, assignment, MISP-linking, and export.
Remote code execution via log path traversal in Flowintel 3.3.0 and later is achievable by an authenticated administrator who redirects the LOG_FILE configuration setting to an arbitrary filesystem path and injects server-side template syntax through attacker-controlled logged content. The upstream commit explicitly documents this multi-step exploitation chain - redirecting log output to a template file and triggering application rendering to execute injected code - making weaponization technically straightforward for any attacker holding admin credentials. No public exploit or CISA KEV listing is identified at time of analysis; upstream fix is available as a GitHub commit from the Flowintel maintainer CIRCL.
Remote code execution in Flowintel's alerts settings update endpoint (versions >= 3.3.0) allows an authenticated high-privileged attacker to inject arbitrary Python statements into the application's live configuration module. The vulnerable endpoint in app/alerts/alerts.py interpolated attacker-supplied configuration keys directly into Python source written to conf/config_module.py, then triggered importlib.reload() - executing injected code in the server process. No public exploit has been identified and the vulnerability is not listed in CISA KEV, but successful exploitation yields full server-side code execution with the privileges of the Flowintel process.
Flowintel's PDF export pipeline passes attacker-controlled note content to Pandoc with the raw_tex extension enabled, allowing authenticated users to inject XeLaTeX directives such as \input{} or \verbatiminput{} that cause the server to read arbitrary local files and embed their contents into the exported PDF. Any authenticated user with note-editing access can exploit this to exfiltrate sensitive server-side files - credentials, keys, or intelligence data stored on the host. No public exploit has been identified at time of analysis, but the LaTeX injection-to-file-read technique is well-documented and requires no specialized tooling.
Log injection in Flowintel versions 3.3.0 and later allows unauthenticated remote attackers to forge arbitrary log lines by supplying email values containing CR/LF characters at the login endpoint. The vulnerability traces to a misuse of WTForms validation - the code constructed a validator object via Email(email) without invoking it, leaving attacker-controlled input unsanitized before it was interpolated into both the standard warning logger and the custom audit logger via Python f-strings. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the attack is trivially executable with a single HTTP request against any network-exposed deployment, and its impact falls directly on security logging integrity rather than application confidentiality or availability.
Stored cross-site scripting in Flowintel's MISP timeline renderer allows an authenticated low-privileged attacker to inject arbitrary HTML into case timelines by supplying malicious content in MISP object fields - including UUID, object name, attribute values, types, comments, first/last seen timestamps, and IDS flags. These fields were concatenated directly into HTML strings without escaping; although DOMPurify was present, the upstream commit explicitly acknowledges it blocked script-based XSS vectors but still permitted other HTML elements such as forms to pass through. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Insufficient authorization on the Flowintel /my_assignment/user API endpoint allows any authenticated API user to retrieve assignment records belonging to other users by supplying an arbitrary user_id parameter. Affected are Flowintel instances up to and including version 3.3.0, per EUVD-2026-67127. The fix, confirmed via commit 10ec32e7, elevates the required privilege level by replacing the api_required decorator with admin_or_org_admin_required, restricting cross-user assignment queries to administrators only. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Stored cross-site scripting in Flowintel's calendar view (versions >= 3.3.0) allows an authenticated user with case-creation or case-editing privileges to inject arbitrary HTML or JavaScript into case titles, which is then executed in the browser of any user who views the calendar. The root cause is unsanitized assignment of user-controlled strings to titleEl.innerHTML. No public exploit has been identified at time of analysis, but the fix is available as an upstream commit and the vulnerability is straightforward to reproduce by any authenticated user.
Stored cross-site scripting in Flowintel case notes allows an authenticated low-privileged user to inject malicious JavaScript via crafted Mermaid diagram blocks, which executes in the browser of any user who subsequently views the affected note. Affected are Flowintel deployments running version 3.3.0 and later; the CVSS 4.0 score of 5.1 reflects that exploitation requires both an authenticated session with note-edit rights and passive victim interaction. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
Stored XSS via Vue template injection in FlowIntel allows an authenticated low-privilege user to persist malicious Vue interpolation expressions across multiple data fields, causing arbitrary JavaScript execution in the browsers of any user who views the poisoned content. The root cause is that Jinja2's standard HTML escaping neutralizes raw HTML tags but does not prevent FlowIntel's custom [[ ... ]] Vue delimiters from being evaluated when the server-rendered output is later compiled by Vue on the client side. Successful exploitation can expose session tokens, sensitive case data, and any information visible to the victim, or perform privileged actions within the victim's authenticated session. No public exploit code or CISA KEV listing has been identified at time of analysis.
Server-side request forgery in FlowIntel up to version 3.3.0 allows a low-privileged authenticated user to coerce the application server into issuing HTTP HEAD requests to attacker-specified destinations-including loopback addresses, RFC 1918 private ranges, link-local cloud metadata endpoints, and other restricted network resources-via the external reference URL probe feature in app/case/task.py. The root cause is absent URL scheme filtering and missing resolved-IP validation before the outbound request is dispatched. No public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV, though the upstream fix commit confirms the flaw's existence and scope.
Persistent session hijacking is possible in Flowintel version 3.3.0 and later because the application fails to invalidate existing authenticated sessions when a user changes their password. An attacker who already holds a valid session token (from prior access or theft) keeps full authenticated access to the account even after the victim resets the password, since the old session remains usable until natural expiry. No public exploit has been identified at time of analysis, and the issue is not in CISA KEV; a vendor fix commit exists.
Privilege escalation in Flowintel's administrative user-edit API allows an organization administrator to modify full administrator accounts within their own organization, including resetting passwords, effectively enabling account takeover of a higher-privileged identity. Affected versions are 3.3.0 and above, as confirmed by upstream commit ffe64d1133b7d84909a69661bd5fee607e9ce757 which adds the missing role-hierarchy boundary check. No public exploit has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Broken object-level authorization across Flowintel task endpoints allows authenticated editor-level users to perform unauthorized operations on tasks belonging to cases they do not own. Flowintel versions >= 3.3.0 accept a case ID and task ID pair on task-related routes but previously failed to verify that the referenced task actually belonged to the supplied case, enabling cross-case data access and manipulation. No public exploit or CISA KEV listing exists at time of analysis, but the CVSS 4.0 score of 7.2 reflects high integrity impact - affected operations include task editing, deletion, note management, file handling, assignment, MISP-linking, and export.
Remote code execution via log path traversal in Flowintel 3.3.0 and later is achievable by an authenticated administrator who redirects the LOG_FILE configuration setting to an arbitrary filesystem path and injects server-side template syntax through attacker-controlled logged content. The upstream commit explicitly documents this multi-step exploitation chain - redirecting log output to a template file and triggering application rendering to execute injected code - making weaponization technically straightforward for any attacker holding admin credentials. No public exploit or CISA KEV listing is identified at time of analysis; upstream fix is available as a GitHub commit from the Flowintel maintainer CIRCL.
Remote code execution in Flowintel's alerts settings update endpoint (versions >= 3.3.0) allows an authenticated high-privileged attacker to inject arbitrary Python statements into the application's live configuration module. The vulnerable endpoint in app/alerts/alerts.py interpolated attacker-supplied configuration keys directly into Python source written to conf/config_module.py, then triggered importlib.reload() - executing injected code in the server process. No public exploit has been identified and the vulnerability is not listed in CISA KEV, but successful exploitation yields full server-side code execution with the privileges of the Flowintel process.
Flowintel's PDF export pipeline passes attacker-controlled note content to Pandoc with the raw_tex extension enabled, allowing authenticated users to inject XeLaTeX directives such as \input{} or \verbatiminput{} that cause the server to read arbitrary local files and embed their contents into the exported PDF. Any authenticated user with note-editing access can exploit this to exfiltrate sensitive server-side files - credentials, keys, or intelligence data stored on the host. No public exploit has been identified at time of analysis, but the LaTeX injection-to-file-read technique is well-documented and requires no specialized tooling.
Log injection in Flowintel versions 3.3.0 and later allows unauthenticated remote attackers to forge arbitrary log lines by supplying email values containing CR/LF characters at the login endpoint. The vulnerability traces to a misuse of WTForms validation - the code constructed a validator object via Email(email) without invoking it, leaving attacker-controlled input unsanitized before it was interpolated into both the standard warning logger and the custom audit logger via Python f-strings. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the attack is trivially executable with a single HTTP request against any network-exposed deployment, and its impact falls directly on security logging integrity rather than application confidentiality or availability.
Stored cross-site scripting in Flowintel's MISP timeline renderer allows an authenticated low-privileged attacker to inject arbitrary HTML into case timelines by supplying malicious content in MISP object fields - including UUID, object name, attribute values, types, comments, first/last seen timestamps, and IDS flags. These fields were concatenated directly into HTML strings without escaping; although DOMPurify was present, the upstream commit explicitly acknowledges it blocked script-based XSS vectors but still permitted other HTML elements such as forms to pass through. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Insufficient authorization on the Flowintel /my_assignment/user API endpoint allows any authenticated API user to retrieve assignment records belonging to other users by supplying an arbitrary user_id parameter. Affected are Flowintel instances up to and including version 3.3.0, per EUVD-2026-67127. The fix, confirmed via commit 10ec32e7, elevates the required privilege level by replacing the api_required decorator with admin_or_org_admin_required, restricting cross-user assignment queries to administrators only. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Stored cross-site scripting in Flowintel's calendar view (versions >= 3.3.0) allows an authenticated user with case-creation or case-editing privileges to inject arbitrary HTML or JavaScript into case titles, which is then executed in the browser of any user who views the calendar. The root cause is unsanitized assignment of user-controlled strings to titleEl.innerHTML. No public exploit has been identified at time of analysis, but the fix is available as an upstream commit and the vulnerability is straightforward to reproduce by any authenticated user.
Stored cross-site scripting in Flowintel case notes allows an authenticated low-privileged user to inject malicious JavaScript via crafted Mermaid diagram blocks, which executes in the browser of any user who subsequently views the affected note. Affected are Flowintel deployments running version 3.3.0 and later; the CVSS 4.0 score of 5.1 reflects that exploitation requires both an authenticated session with note-edit rights and passive victim interaction. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
Stored XSS via Vue template injection in FlowIntel allows an authenticated low-privilege user to persist malicious Vue interpolation expressions across multiple data fields, causing arbitrary JavaScript execution in the browsers of any user who views the poisoned content. The root cause is that Jinja2's standard HTML escaping neutralizes raw HTML tags but does not prevent FlowIntel's custom [[ ... ]] Vue delimiters from being evaluated when the server-rendered output is later compiled by Vue on the client side. Successful exploitation can expose session tokens, sensitive case data, and any information visible to the victim, or perform privileged actions within the victim's authenticated session. No public exploit code or CISA KEV listing has been identified at time of analysis.
Server-side request forgery in FlowIntel up to version 3.3.0 allows a low-privileged authenticated user to coerce the application server into issuing HTTP HEAD requests to attacker-specified destinations-including loopback addresses, RFC 1918 private ranges, link-local cloud metadata endpoints, and other restricted network resources-via the external reference URL probe feature in app/case/task.py. The root cause is absent URL scheme filtering and missing resolved-IP validation before the outbound request is dispatched. No public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV, though the upstream fix commit confirms the flaw's existence and scope.