Quick answers
- Is CVE-2026-72586 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72586 being exploited in the wild.
- How severe is CVE-2026-72586?
- High severity, with a CVSS score of 7.5, published 10 August 2026.
- Which products and versions are affected?
- Frangoteam FUXA through 1.3.3.
- Is there a fix for CVE-2026-72586?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-72586 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-72586?
- Check whether you run Frangoteam FUXA 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
FUXA contains an authentication bypass vulnerability in the DAQ_QUERY Socket.IO event handler located in server/runtime/index.js. While other sensitive Socket.IO events (DEVICE_BROWSE, HOST_INTERFACES, DEVICE_TAGS_REQUEST, etc.) correctly call isSocketAdminAuthorized to verify connection tokens when secureEnabled=true, the DAQ_QUERY handler entirely lacks this authentication check. An unauthenticated remote attacker can connect via Socket.IO and invoke DAQ_QUERY to retrieve historical sensor data without credentials. The vulnerability affects FUXA through version 1.3.3 and requires network access to the Socket.IO endpoint but no user interaction or authentication.
Affected products
- frangoteam FUXA through 1.3.3
Timeline
- 2026-08-10: disclosed