Quick answers
- Is CVE-2026-81818 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81818 being exploited in the wild.
- How severe is CVE-2026-81818?
- Informational severity, published 27 August 2026.
- Which products and versions are affected?
- FlowIntel >=3.3.0.
- Is there a fix for CVE-2026-81818?
- A patch was published on 2026-08-18. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81818 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-81818?
- 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 an authorization bypass in the user-edit API endpoint (app/admin/admin_api.py). The authorization check correctly prevented organization administrators from editing users in other organizations, but failed to prevent them from editing full administrator accounts within their own organization. The root cause is a missing privilege boundary check: when an org admin attempts to modify a full admin, the code did not verify the target user's admin status. An authenticated organization administrator can exploit this by sending a PATCH/POST request to the user-edit API with credentials of a full admin and parameters to modify (e.g., password change). The fix adds an explicit check: if the target user has admin privileges, org admins receive a 403 Forbidden response. No exploitation in the wild has been reported.
Affected products
- Flowintel Flowintel >=3.3.0
Timeline
- 2026-08-27: disclosed
- 2026-08-18: patched