Quick answers
- Is CVE-2026-81662 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81662 being exploited in the wild.
- How severe is CVE-2026-81662?
- Informational severity, with a CVSS score of 8.8, published 27 August 2026.
- Which products and versions are affected?
- FlowIntel 3.3.0 and later.
- Is there a fix for CVE-2026-81662?
- A patch was published on 2026-08-27: Fix available in commit d36171e Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81662 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-81662?
- 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 code injection flaw in the alerts settings update endpoint that processes configuration keys and values. While configuration values are sanitized into Python literals, the keys are used directly in string formatting to generate Python source code (f'{key} = {py_val}'), which is then written to and reloaded from conf/config_module.py using importlib.reload(). An attacker can supply specially crafted configuration keys containing Python syntax to break out of the assignment context and inject arbitrary statements. The attack requires network access to the alerts settings endpoint and the ability to send a crafted request; no authentication bypass is explicitly documented but endpoint access controls should be verified. The fix, available in commit d36171e, properly sanitizes configuration keys to prevent syntax injection.
Affected products
- Flowintel Flowintel 3.3.0 and later
Timeline
- 2026-08-27: disclosed: Published on NVD
- 2026-08-27: patched: Fix available in commit d36171e