# CVE-2026-65985: FUXA: SSRF hardening for `device-webapi-request`

> Authenticated users can exploit an SSRF vulnerability in FUXA to read responses from internal services or cloud metadata endpoints via the server.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-wrg6-49wh-46pw

## What is CVE-2026-65985?

CVE-2026-65985 is a medium-severity server-side request forgery vulnerability in frangoteam FUXA, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In 1.3.2 and earlier, the device-webapi-request Socket.IO handler in server/runtime/index.js permits an authenticated non-admin runtime user to control property.address, causing the FUXA server to issue an outbound HTTP or HTTPS request and return the response body to the requesting socket. The attacker can use the server as a read SSRF oracle against reachable internal services or cloud metadata endpoints, with impact depending on the FUXA host's deployment network. This issue is fixed in version 1.3.3.

Weakness: CWE-918 (Server-Side Request Forgery)

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


## How do I fix CVE-2026-65985?

No fix has been published for CVE-2026-65985 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-65985 being exploited?

There is no known exploitation of CVE-2026-65985 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65985 is a medium-severity server-side request forgery vulnerability in frangoteam FUXA, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65985 in the wild and no public exploit code.

Affected product: frangoteam FUXA. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-65985/ (Markdown: https://insights.sbomify.com/CVE-2026-65985/index.md)
```

## Sources

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

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