Skip to main content

Flowintel EUVDEUVD-2026-67007

| CVE-2026-81743 HIGH
Path Traversal (CWE-22)
2026-08-27 CIRCL GHSA-jhj7-jmh6-rrgr
7.5
CVSS 4.0 · Vendor: CIRCL
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Flowintel admin credentials
  2. Delivery
    Redirect LOG_FILE to writable template path
  3. Exploit
    Submit Jinja2 payload via logged user input
  4. Execution
    Application writes payload to redirected file
  5. Persist
    Trigger template rendering via normal application flow
  6. Impact
    Execute arbitrary OS commands

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated Flowintel session with administrator privileges, which grants access to the system settings panel where LOG_FILE was web-editable prior to the patch. The target instance must be running Flowintel version 3.3.0 or later. The attacker must identify an application code path that both logs attacker-controlled content and subsequently causes the Jinja2 template engine to render the redirected log file - a specific rendering trigger documented in the upstream commit. Default installations where LOG_FILE has never been modified are not directly exploitable without first changing the setting. Exploitation is concretely limited by: administrator-level authentication (PR:H per CVSS 4.0 vector), the multi-step chaining of path redirection and template injection (AC:H), and the requirement for a specific rendering condition to be met (AT:P). Unauthenticated users and non-administrator authenticated users cannot exploit this vulnerability.

Impact

The CVSS 4.0 vector (AV:N/AC:H/AT:P/PR:H/UI:N, score 7.5) correctly reflects a high-impact but access-constrained vulnerability. PR:H is the dominant limiting factor: exploitation is gated behind administrator-level credentials, meaning an attacker must either compromise admin credentials or be an insider threat before the path traversal becomes relevant. AC:H and AT:P further indicate the attack chain is multi-step and depends on specific application rendering conditions. No EPSS score was provided in source data, and the vulnerability is absent from CISA KEV, indicating no confirmed active exploitation at time of analysis. The technical impact if successfully exploited is severe - full RCE with OS-level code execution under the Flowintel process account - making this a high-value post-compromise escalation primitive. The realistic threat model is insider abuse or an attacker who obtained admin credentials through a prior compromise (credential stuffing, phishing, or a separate vulnerability). The 7.5 score is well-calibrated: the high impact metrics are real, but PR:H and AC:H substantially contain opportunistic exploitability.

Exploit ScenarioDerived

An attacker with administrative access to Flowintel's web interface navigates to system settings and changes LOG_FILE to a filesystem path pointing to a Jinja2 template file writable by the Flowintel process - for example, overwriting an existing application template. The attacker then submits case data or another logged input field containing a Jinja2 payload (such as a reverse shell via subprocess) that the application writes to the redirected path. When the application subsequently serves a page that renders the tampered template, the injected code executes with the privileges of the Flowintel web process, yielding full server access.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

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.

RemediationAI

Upstream fix is available (commit); a tagged patched release version is not independently confirmed from available data. Administrators should update to a Flowintel build incorporating commit 13785ee5d70a54d0ac97ba89dd31a478a86fc161, available at https://github.com/flowintel/flowintel/commit/13785ee5d70a54d0ac97ba89dd31a478a86fc161. If immediate patching is not feasible, restrict administrative access to the Flowintel web interface to trusted internal networks or VPN-enforced access to reduce the attack surface for credential-based escalation - note this does not eliminate risk for insider threats or already-compromised admin accounts. As an additional compensating control, audit the current LOG_FILE value in system settings and verify it contains only a simple filename with no path separators, absolute path indicators, or traversal sequences; any abnormal value should be treated as an indicator of potential exploitation. After patching, LOG_FILE becomes a CLI-only configuration parameter and will no longer appear as an editable field in the web settings panel, which is the intended post-fix behavior.

Affected VersionsENISA

flowintel 0 ≤3.3.0

Affected Packages

euvd flowintel no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Flowintel is a Flask-based threat intelligence case management platform developed by CIRCL (Computer Incident Response Center Luxembourg), using Jinja2 as its template engine - the same engine that makes log-to-template injection executable. The affected CPE is cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* for versions 3.3.0 and later. The root cause is CWE-22 (Path Traversal): LOG_FILE was accepted from the web settings API and passed directly to os.path.join() without sanitization, allowing absolute paths and directory traversal sequences to escape the intended logs/ directory. Because Flask/Jinja2 renders template files at request time, redirecting log writes to a Jinja2 template file enables server-side template injection (SSTI) leading to arbitrary Python execution. The patch introduces validate_log_file_name() in app/utils/log_paths.py, which rejects absolute paths, Windows absolute paths (via PureWindowsPath - explaining the 'Microsoft' tag in the CVE metadata), null bytes, traversal sequences, and any value containing directory separators. All log path resolution is centralized through resolve_log_file_path(), and LOG_FILE is removed from the web-editable settings panel entirely, becoming a CLI-only configuration parameter.

Know when Flowintel gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (CIRCL) PRIMARY 7.5 HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 6.6 MEDIUM

Administrator web access required (PR:H), multi-step template injection chain (AC:H), full RCE impact on the application server with scope unchanged.

3.1 AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (CIRCL).

CVSS VectorVendor: CIRCL

Attack Vector
Network
Attack Complexity
High
Attack Requirements
Present
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Affected versions of Flowintel allow the LOG_FILE configuration value to be modified through system settings without restricting it to a filename inside the intended log directory.

Because the application constructs the log destination from this configurable value, an administrator could set LOG_FILE to an arbitrary filesystem path. Since attackers can influence logged content, this enables controlled data to be written into unintended files. The upstream commit specifically describes an exploitation chain in which an attacker injects a template into a chosen file and subsequently abuses application rendering behavior to execute code.

The patch removes LOG_FILE from the web-editable settings, introduces validate_log_file_name() to reject absolute paths, traversal, Windows paths, null bytes, and directory components, and centralizes log path construction through resolve_log_file_path().

Version impacted: >=3.3.0

Executive ViewAI

Why It Matters

Flowintel versions 3.3.0 and later are vulnerable to remote code execution if administrator accounts are compromised; no public exploit code is identified at time of analysis. An attacker with admin credentials can manipulate logging configurations to inject and execute malicious code within the application. Organizations should patch immediately and review administrator access controls to prevent system compromise.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 76% exploitable
Prevalence
Low
niche threat intelligence platform, primarily CERT and SOC deployments
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

CVE-2026-81826 CRITICAL
9.1 Aug 27

Persistent session hijacking is possible in Flowintel version 3.3.0 and later because the application fails to invalidat

CVE-2026-81662 HIGH
8.6 Aug 27

Remote code execution in Flowintel's alerts settings update endpoint (versions >= 3.3.0) allows an authenticated high-pr

CVE-2026-81818 HIGH
8.6 Aug 27

Privilege escalation in Flowintel's administrative user-edit API allows an organization administrator to modify full adm

CVE-2026-81817 HIGH
7.2 Aug 27

Broken object-level authorization across Flowintel task endpoints allows authenticated editor-level users to perform una

CVE-2026-81659 HIGH
7.1 Aug 27

Flowintel's PDF export pipeline passes attacker-controlled note content to Pandoc with the raw_tex extension enabled, al

CVE-2026-81827 MEDIUM
6.9 Aug 27

Log injection in Flowintel versions 3.3.0 and later allows unauthenticated remote attackers to forge arbitrary log lines

CVE-2026-69075 MEDIUM
6.9 Aug 03

Stored XSS via Vue template injection in FlowIntel allows an authenticated low-privilege user to persist malicious Vue i

CVE-2026-9813 MEDIUM
6.2 May 28

Server-side request forgery in FlowIntel up to version 3.3.0 allows a low-privileged authenticated user to coerce the ap

CVE-2026-81819 MEDIUM
5.3 Aug 27

Insufficient authorization on the Flowintel /my_assignment/user API endpoint allows any authenticated API user to retrie

CVE-2026-81753 MEDIUM
5.1 Aug 27

Stored cross-site scripting in Flowintel case notes allows an authenticated low-privileged user to inject malicious Java

CVE-2026-81814 MEDIUM
5.1 Aug 27

Stored cross-site scripting in Flowintel's calendar view (versions >= 3.3.0) allows an authenticated user with case-crea

CVE-2026-81820 MEDIUM
5.1 Aug 27

Stored cross-site scripting in Flowintel's MISP timeline renderer allows an authenticated low-privileged attacker to inj

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy