CVE-2026-133620: Flowintel Template Repository Path Traversal and Symlink Escape Allows Arbitrary File Read

Published Nov 20, 2026
·
Updated

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 REPOSITORYBASEPATH, 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.

Affected Software

1 affected component
FlowIntel FlowIntel<4.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.1.0

Event History

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

Frequently Asked Questions

1

Which deployments are affected?

Flowintel versions prior to 4.1.0 are affected. Exploitation is limited to files that the Flowintel service account can read on the host.

2

What access does an attacker need to exploit this issue?

An attacker needs an authenticated Flowintel account with permission to add or edit a template repository. No user interaction is required.

3

Are default repository restrictions sufficient protection?

No. The affected implementation accepted repository paths outside the configured REPOSITORY_BASE_PATH, and its path validation could also be bypassed using symbolic links.

4

What can an attacker obtain?

An attacker can cause Flowintel to return arbitrary readable files from the host, potentially including configuration files, credentials, and other sensitive data accessible to the service account.

5

What should be done if upgrading is not immediately possible?

Restrict the ability to add or edit template repositories to only highly trusted users. Reduce the Flowintel service account's filesystem permissions so it cannot read credentials or other sensitive files unnecessarily.

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