Unauthenticated device manipulation via Socket.IO authorization gap
Published Feb 6, 2026 · Updated Feb 6, 2026
Missing authorization in FUXA before 1.2.10 allows remote attackers to write device tags or disable drivers through Socket.IO. The runtime Socket.IO layer accepts guest device-values requests with cmd set and device-enable actions without enforcing authorization for write and device-management operations. No authentication or user interaction is required, and even secure-enabled deployments expose connected control processes to unauthorized value changes or communication loss.
Summary
What happened
Missing authorization in FUXA before 1.2.10 allows remote attackers to write device tags or disable drivers through Socket.IO. The runtime Socket.IO layer accepts guest device-values requests with cmd set and device-enable actions without enforcing authorization for write and device-management operations. No authentication or user interaction is required, and even secure-enabled deployments expose connected control processes to unauthorized value changes or communication loss.
The record
- CVE
- CVE-2026-25752
- Published
- Feb 6, 2026
- Updated
- Feb 6, 2026
- Vendor
- Frangoteam
- Product
- FUXA
- Classifications
- CWE-862, T0831
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2026CVE publishedPublication date reported by the CVE source.
- Feb 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo