# 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.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-w86f-rf9w-h3x6

## 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 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-47719?

2 open source packages ship an affected version, including fuxa-server.


| Package | Ecosystem | 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.

## Is CVE-2026-47719 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47719 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47719 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47719 exists.

Affected packages and fixed versions:
- fuxa-server (npm): affected all versions up to 1.1.14-1243; no fix listed
- fuxa-server (npm): affected all versions up to 1.1.14-1243; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47719/ (Markdown: https://insights.sbomify.com/CVE-2026-47719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47719
- OSV: https://osv.dev/vulnerability/CVE-2026-47719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47719/
Summaries are generated and may contain mistakes; the official description above is the record.