# CVE-2026-67440: FUXA: Unauthenticated Socket.IO read events

> Unauthenticated users can access sensitive device and host metadata in FUXA when secure mode is enabled, exposing system discovery information.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** 19 Aug 2026
- **Also known as:** GHSA-rh5p-m38p-2w75

## What is CVE-2026-67440?

CVE-2026-67440 is a medium-severity missing authorization 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. In 1.3.2 and earlier, the DEVICE_BROWSE, DEVICE_NODE_ATTRIBUTE, HOST_INTERFACES, and DEVICE_TAGS_REQUEST handlers in server/runtime/index.js return device-discovery, node-attribute, host-network-interface, and device-tag metadata without isSocketAdminAuthorized when secureEnabled is true. A remote unauthenticated or guest user can invoke these metadata-oriented Socket.IO events and collect system-discovery information that is not required for normal public HMI viewing, while ordinary device status, value, alarm, and dashboard events remain intentionally public. This issue is fixed in version 1.3.3.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-67440 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67440 is a medium-severity missing authorization 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: There is no known exploitation of CVE-2026-67440 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-67440/ (Markdown: https://insights.sbomify.com/CVE-2026-67440/index.md)
```

## Sources

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

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