# CVE-2026-25951: FUXA has a Path Traversal Sanitization Bypass

> An authenticated administrator can bypass path sanitization to write arbitrary files, leading to remote code execution in FUXA SCADA software.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Feb 2026
- **Updated:** 11 Feb 2026
- **Also known as:** GHSA-68m5-5w2h-h837

## What is CVE-2026-25951?

CVE-2026-25951 is a high-severity path traversal vulnerability in frangoteam FUXA, published on 9 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.2.11, there is a flaw in the path sanitization logic allows an authenticated attacker with administrative privileges to bypass directory traversal protections. By using nested traversal sequences (e.g., ....//), an attacker can write arbitrary files to the server filesystem, including sensitive directories like runtime/scripts. This leads to Remote Code Execution (RCE) when the server reloads the malicious scripts. This vulnerability is fixed in 1.2.11.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-184 (Incomplete List of Disallowed Inputs)

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

2 open source packages ship an affected version, including fuxa-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fuxa-server` | npm | All versions | 1.2.11 |
| `fuxa-server` | npm | All versions | 1.2.11 |

Products: Frangoteam Fuxa.

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

Upgrade fuxa-server to 1.2.11 or later.

## Is CVE-2026-25951 being exploited?

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

## Other vulnerabilities in frangoteam FUXA

- [CVE-2026-25893](https://insights.sbomify.com/CVE-2026-25893/): FUXA Unauthenticated Remote Code Execution via Admin JWT Minting (critical 10.0)
- [CVE-2025-69985](https://insights.sbomify.com/CVE-2025-69985/): FUXA has JWT Authentication Bypass via HTTP Referer header spoofing (critical 9.8)
- [CVE-2025-69971](https://insights.sbomify.com/CVE-2025-69971/): FUXA has a hardcoded fallback JWT signing secret (critical 9.8)
- [CVE-2023-31719](https://insights.sbomify.com/CVE-2023-31719/): FUXA SQL Injection vulnerability (critical 9.8)
- [CVE-2023-33831](https://insights.sbomify.com/CVE-2023-33831/): A remote command execution (RCE) vulnerability in the /api/runscript endpoint of FUXA (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25951 is a high-severity path traversal vulnerability in frangoteam FUXA, published on 9 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25951 in the wild and no public exploit code.

Affected packages and fixed versions:
- fuxa-server (npm): affected all versions; fixed in 1.2.11
- fuxa-server (npm): affected all versions; fixed in 1.2.11

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

## Sources

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

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