CVE-2026-47719 FUXA: Unauthenticated SSRF via Socket.IO DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY with response reading
Unauthenticated attackers can exploit Socket.IO handlers to perform Server-Side Request Forgery, accessing internal services and cloud metadata.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-47719?
CVE-2026-47719 is a high-severity server-side request forgery vulnerability in frangoteam FUXA, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, the DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY Socket.IO handlers in server/runtime/index.js omit isSocketWriteAuthorized and accept attacker-controlled property.address or endpoint connection data. A remote unauthenticated attacker can make server/runtime/devices/httprequest/index.js call axios.get against arbitrary HTTP or HTTPS destinations, connect to reachable OPC UA or ODBC services, and receive results through the corresponding Socket.IO event. This read SSRF oracle can expose cloud instance metadata, internal administrative services, industrial endpoints, and ODBC data reachable from the FUXA host, including when secureEnabled is true. This issue is fixed in version 1.3.2.
Weakness: CWE-918
Which versions are affected by CVE-2026-47719?
2 open source packages ship an affected version, including fuxa-server.
| Package | Affected | Fixed in |
|---|---|---|
fuxa-server npm | All versions to 1.1.14-1243 | None |
fuxa-server npm | All versions to 1.1.14-1243 | None |
How do I fix CVE-2026-47719?
No fix has been published for CVE-2026-47719 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-47719 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47719 exists.
Sources
Also known as GHSA-w86f-rf9w-h3x6.