Quick answers
- Is CVE-2026-44352 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44352 being exploited in the wild.
- How severe is CVE-2026-44352?
- Informational severity, with a CVSS score of 5.3, published 12 May 2026.
- Which products and versions are affected?
- Reconurge Flowsint < 1.2.3.
- Is there a fix for CVE-2026-44352?
- A patch was published on 2026-05-12: Vulnerability fixed in version 1.2.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44352 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44352?
- Check whether you run Reconurge Flowsint 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
A broken access control vulnerability exists in Flowsint's API due to improper authorization checks in the scan and event routes. Specifically, the `/api/scans` endpoint leaks `sketch_id` values for all scans in the database because it lacks ownership filtering. Furthermore, the `/api/events/sketch/{sketch_id}/logs` endpoint has the `current_user` dependency commented out in the source code, allowing any authenticated user to query logs for any valid `sketch_id`. An attacker can exploit this to monitor 'transformers' (automated processes) run by other users and extract graph data, such as node labels and relationships, via 'GRAPH_APPEND' payloads in the logs. This issue is resolved in version 1.2.3.
Affected products
- reconurge Flowsint < 1.2.3
Timeline
- 2026-05-06: advisory: GitHub Security Advisory published
- 2026-05-12: disclosed: CVE published to NVD
- 2026-05-12: patched: Vulnerability fixed in version 1.2.3