Quick answers
- Is CVE-2026-25752 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25752 being exploited in the wild.
- How severe is CVE-2026-25752?
- Medium severity, with a CVSS score of 4, published 5 February 2026.
- Which products and versions are affected?
- fuxa-server (npm) SEMVER:introduced=0,fixed=1.2.10.
- Is there a fix for CVE-2026-25752?
- Yes. fuxa-server (npm): upgrade to 1.2.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-25752 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-25752?
- Check whether you run fuxa-server (npm) 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.
How to fix
- fuxa-server (npm): upgrade to 1.2.10 or later
npm install fuxa-server@1.2.10
Technical details
The vulnerability is an authorization bypass (CWE-862) in the WebSocket communication layer of FUXA that fails to enforce authentication and role-based access controls when processing device tag modification requests. An unauthenticated, network-reachable attacker can craft WebSocket messages to overwrite arbitrary device tags or disable communication drivers without requiring credentials or user interaction. The vulnerability affects all versions through 1.2.9, including deployments with runtime.settings.secureEnabled set to true. It has been patched in FUXA version 1.2.10.
Affected products
- FUXA FUXA <=1.2.9
Identifiers
- CVE-2026-25752
- GHSA-ggxw-g3cp-mgf8
Timeline
- 2026-02-05: disclosed
- 2026-02-05: patched: Fixed in version 1.2.10