# CVE-2026-25895: FUXA Unauthenticated Remote Code Execution via Arbitrary File Write in Upload API

> Unauthenticated attackers can write arbitrary files to the server filesystem via path traversal, leading to remote code execution in FUXA.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Feb 2026
- **Updated:** 11 Feb 2026
- **Also known as:** GHSA-88qh-cphv-996c

## What is CVE-2026-25895?

CVE-2026-25895 is a critical path traversal vulnerability in frangoteam FUXA, published on 9 Feb 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. A path traversal vulnerability in FUXA allows an unauthenticated, remote attacker to write arbitrary files to arbitrary locations on the server filesystem. This affects FUXA through version 1.2.9. This issue has been patched in FUXA version 1.2.10.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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.10 |
| `fuxa-server` | npm | All versions | 1.2.10 |

Products: Frangoteam Fuxa.

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

Upgrade fuxa-server to 1.2.10 or later.

## Is CVE-2026-25895 being exploited?

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

Public exploit code:

- POC exploit for CVE-2026-25895 FUXA Unauthenticated Path Traversal -> Arbitrary File Write -> RCE (github_poc): https://github.com/Hann1bl3L3ct3r/FUXAPWN
- FUXA  1.2.9 -  RCE (exploitdb)
- FUXA <= 1.2.9 - Unauthenticated Path Traversal to Arbitrary File Write (nuclei): http/cves/2026/CVE-2026-25895.yaml

## 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-25895 and fix it if it is affected.

What it is: CVE-2026-25895 is a critical path traversal vulnerability in frangoteam FUXA, published on 9 Feb 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-25895 exists.

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

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

## Sources

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

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