Quick answers
- Is CVE-2026-67440 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67440 being exploited in the wild.
- How severe is CVE-2026-67440?
- Informational severity, published 18 August 2026.
- Which products and versions are affected?
- Frangoteam FUXA 1.3.2 and earlier.
- Is there a fix for CVE-2026-67440?
- A patch was published on 2026-05-25: Fix released in version 1.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67440 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-67440?
- 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
The vulnerability is an authentication bypass affecting Socket.IO event handlers (DEVICE_BROWSE, DEVICE_NODE_ATTRIBUTE, HOST_INTERFACES, and DEVICE_TAGS_REQUEST) in FUXA versions 1.3.2 and earlier. When secureEnabled is true, these handlers fail to enforce the isSocketAdminAuthorized check before returning device-discovery, node-attribute, host-network-interface, and device-tag metadata. An unauthenticated or guest user can directly invoke these events over the Socket.IO connection to enumerate system topology and configuration details. The vulnerability was remedied in version 1.3.3 by adding proper authorization enforcement. Attack requires only network reachability to the web-based FUXA interface; no authentication or user interaction is required.
Affected products
- frangoteam FUXA 1.3.2 and earlier
Timeline
- 2026-08-18: disclosed
- 2026-05-25: patched: Fix released in version 1.3.3