{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81743 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81743 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81743 is a high-severity code injection vulnerability in flowintel, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81743 and fix it if it is affected.\n\nWhat it is: CVE-2026-81743 is a high-severity code injection vulnerability in flowintel, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81743 in the wild and no public exploit code.\n\nAffected product: flowintel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81743/ (Markdown: https://insights.sbomify.com/CVE-2026-81743/index.md)","id":"CVE-2026-81743","markdown":"https://insights.sbomify.com/CVE-2026-81743/index.md","name":"CVE-2026-81743","record":{"aliases":["GHSA-jhj7-jmh6-rrgr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Flowintel application","requires_auth":"high_privilege","summary":"Attackers can achieve remote code execution by manipulating log file paths to inject templates, requiring patching of Flowintel.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.\n\nBecause 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.\n\nThe 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().\n\nVersion impacted: \u003e=3.3.0","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Flowintel Arbitrary Log File Path Allows Remote Code Execution via Template Injection","id":"CVE-2026-81743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Flowintel Stored XSS in Case Notes via Malicious Mermaid Diagram Content","id":"CVE-2026-81753"},"packages":[],"prev":{"headline":"BE REST Endpoints \u003c= 1.0.0 - Unauthenticated Stored XSS and Widget Manipulation","id":"CVE-2026-81742"},"products":["flowintel"],"published":"2026-08-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["flowintel"]},"summary":"Attackers can achieve remote code execution by manipulating log file paths to inject templates, requiring patching of Flowintel.","url":"https://insights.sbomify.com/CVE-2026-81743/"}