- Repository registration and editing accepted arbitrary local paths without verifying they resolved inside the configured REPOSITORY_BASE_PATH, allowing an authenticated user to point a repository at any readable directory on the host.
- Manifest and template file lookups used normalized (non-canonical) path joins and a startswith-based guard that could be bypassed by symbolic links, permitting reads of files outside the intended repository.
An authenticated user with the ability to add or edit a template repository could therefore cause the application to read and return the contents of arbitrary files readable by the service account, including configuration files, credentials, or other sensitive data.
Affected: Flowintel versions prior to 4.1.0.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
The fix introduces canonical (realpath-based) path resolution and enforces that every repository root and every child file or directory resolves within the configured REPOSITORY_BASE_PATH using os.path.commonpath. All code paths that previously performed raw os.path.join or normpath operations (registration, editing, discovery scan, entry scan, manifest read, and template file read) now go through the new validated helpers. Scans that encounter an escaping path roll back any partial database updates and return an error, preventing partial state corruption.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 20 Nov 2026 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Flowintel's template repository subsystem did not adequately constrain file access to the configured repository base directory. Two related weaknesses existed: - Repository registration and editing accepted arbitrary local paths without verifying they resolved inside the configured REPOSITORY_BASE_PATH, allowing an authenticated user to point a repository at any readable directory on the host. - Manifest and template file lookups used normalized (non-canonical) path joins and a startswith-based guard that could be bypassed by symbolic links, permitting reads of files outside the intended repository. An authenticated user with the ability to add or edit a template repository could therefore cause the application to read and return the contents of arbitrary files readable by the service account, including configuration files, credentials, or other sensitive data. Affected: Flowintel versions prior to 4.1.0. | |
| Title | Flowintel Template Repository Path Traversal and Symlink Escape Allows Arbitrary File Read | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-22 CWE-59 |
|
| 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:18:09.557Z
Reserved: 2026-11-20T08:18:07.900Z
Link: CVE-2026-133620
No data.
No data.
No data.
OpenCVE Enrichment
No data.