Quick answers
- Is CVE-2026-81743 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81743 being exploited in the wild.
- How severe is CVE-2026-81743?
- Informational severity, with a CVSS score of 7.2, published 27 August 2026.
- Which products and versions are affected?
- FlowIntel >=3.3.0.
- Is there a fix for CVE-2026-81743?
- A patch was published on 2026-08-18: Security fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81743 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-81743?
- Check whether you run FlowIntel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a path traversal and remote code execution flaw in Flowintel's logging configuration. The LOG_FILE setting was editable through the web interface without validation, allowing administrators (or attackers with admin privileges) to redirect logs to arbitrary filesystem paths. An attacker can inject malicious template content into logs through application functionality, and when the application renders these logs, the injected template is executed as code. The patch removes LOG_FILE from web-editable settings, adds validate_log_file_name() to reject absolute paths, directory traversal sequences, and other dangerous patterns, and centralizes path resolution through resolve_log_file_path(). Attack requires admin-level access and knowledge of the application's logging and rendering behavior.
Affected products
- Flowintel Flowintel >=3.3.0
Timeline
- 2026-08-27: disclosed: CVE-2026-81743 published
- 2026-08-18: patched: Security fix committed to repository