CVE-2026-25951: Fuxa server Path Traversal Vulnerability

HIGH
Advisory Identifier: GHSA-68m5-5w2h-h837
Share
CWE-23 CWE-184 CWE-22
Published
Advisory Summary

CVE-2026-25951 is a HIGH path traversal vulnerability (CWE-23: Relative Path Traversal) affecting Fuxa server libraries in the npm ecosystem. The issue involves fuxa affected by a path traversal sanitization bypass. Remediation is available by upgrading affected packages to version 1.2.11.

CVE-2026-25951 at a Glance

CVE Identifier CVE-2026-25951
GHSA Identifier GHSA-68m5-5w2h-h837
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-23: Relative Path Traversal
Affected Product Fuxa server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-25951

To remediate this vulnerability, upgrade all affected Fuxa server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

fuxa-server fixed: 1.2.11 
npm install fuxa-server@1.2.11
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls fuxa-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-25951, inspect your project dependencies using npm:

npm ls fuxa-server

Analyze the terminal output to locate any version of Fuxa server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.11), your application is affected.

Note: The npm ls fuxa-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-23: Relative Path Traversal, where the product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. In Fuxa server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. It is a new vulnerability a patch bypass for the sanitization in the last release . ### Details This report describes a new, distinct vulnerability that differs from previous Path Traversal advisories (such as CVE-2023-31718) in several ways: Patch Bypass (Regression): The vulnerability circumvents the existing sanitization logic implemented to fix previous traversal issues. The current "single-pass" regex approach is insufficient against nested sequences. Expansion of Scope: Unlike previous reports that focused primarily on /api/download, this bypass affects multiple critical endpoints, including /api/upload, /api/resources/remove, and /api/logs. Escalation to RCE: By targeting the upload and remove functionalities, this vulnerability directly leads to Remote Code Execution, which is a higher impact than the information disclosure typically associated with previous traversal reports. ### Impact Remote Code Execution (RCE): Transition from application admin to full system control. SCADA Operational Disruption: Potential for physical or operational sabotage by manipulating tags and alarms. Data Integrity & Availability: Full access to projects, credentials, and historical logs. ### Patches This issue has been patched in FUXA version 1.2.11. Users are strongly encouraged to update to the latest available release.

CVE-2026-25951 Affected Fuxa server Versions

1 component(s)
Fixed Versions:
1.2.11
Product / Package Ecosystem Affected Versions Fixed Version
fuxa-server
npm/fuxa-server
npm
< 1.2.11
1.2.11

References

GitHub Advisory / Wiki ADVISORY
https://github.com/frangoteam/FUXA/security/advisories/GHSA-68m5-5w2h-h837
NVD — CVE-2026-25951 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-25951
Fuxa server Source Repository REPOSITORY
https://github.com/frangoteam/FUXA/pull/2177
Security Fix Commit FIX COMMIT
https://github.com/frangoteam/FUXA/commit/3ecce46333ed33e3f66f378e38e317cde702b0ae
Security Fix Commit FIX COMMIT
https://github.com/frangoteam/FUXA/commit/f7a9f04b2ab97ab5421e4ec4e711c51e9f4b65c8
Fuxa server Source Repository REPOSITORY
https://github.com/frangoteam/FUXA
Fuxa server Release RELEASE
https://github.com/frangoteam/FUXA/releases/tag/v1.2.11

Frequently Asked Questions

What is CVE-2026-25951?
CVE-2026-25951 is a security vulnerability in Fuxa server involving FUXA Affected by a Path Traversal Sanitization Bypass under CWE-23: Relative Path Traversal.
Which Fuxa server versions are affected?
Affected versions include releases prior to 1.2.11 across affected packages: fuxa-server.
What version fixes CVE-2026-25951?
Upgrading to 1.2.11 (or the latest patched release for your respective branch) resolves the vulnerability.
Is fuxa-server affected?
Yes, fuxa-server is affected in releases prior to 1.2.11. Upgrade your dependency to 1.2.11 or later.
What CWE is associated with CVE-2026-25951?
CVE-2026-25951 is classified under CWE-23: Relative Path Traversal (The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.).
How can I check npm dependencies for CVE-2026-25951?
Run the dependency tree command: 'npm ls fuxa-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-68m5-5w2h-h837",
  "modified" : "2026-02-10T14:18:49Z",
  "published" : "2026-02-10T00:29:00Z",
  "aliases" : [ "CVE-2026-25951" ],
  "summary" : "FUXA Affected by a Path Traversal Sanitization Bypass",
  "details" : "### Summary\nA 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. It is a new vulnerability a patch bypass for the sanitization in the last release .\n\n\n### Details\nThis report describes a new, distinct vulnerability that differs from previous Path Traversal advisories (such as CVE-2023-31718) in several ways:\n\nPatch Bypass (Regression): The vulnerability circumvents the existing sanitization logic implemented to fix previous traversal issues. The current \"single-pass\" regex approach is insufficient against nested sequences.\nExpansion of Scope: Unlike previous reports that focused primarily on /api/download, this bypass affects multiple critical endpoints, including /api/upload, /api/resources/remove, and /api/logs.\nEscalation to RCE: By targeting the \nupload\n and remove functionalities, this vulnerability directly leads to Remote Code Execution, which is a higher impact than the information disclosure typically associated with previous traversal reports.\n\n\n### Impact\nRemote Code Execution (RCE): Transition from application admin to full system control.\nSCADA Operational Disruption: Potential for physical or operational sabotage by manipulating tags and alarms.\nData Integrity & Availability: Full access to projects, credentials, and historical logs.\n\n### Patches\n\nThis issue has been patched in FUXA version 1.2.11. Users are strongly encouraged to update to the latest available release.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "fuxa-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2.11"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.2.10"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/frangoteam/FUXA/security/advisories/GHSA-68m5-5w2h-h837"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-25951"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/frangoteam/FUXA/pull/2177"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/frangoteam/FUXA/commit/3ecce46333ed33e3f66f378e38e317cde702b0ae"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/frangoteam/FUXA/commit/f7a9f04b2ab97ab5421e4ec4e711c51e9f4b65c8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/frangoteam/FUXA"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/frangoteam/FUXA/releases/tag/v1.2.11"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-184", "CWE-22", "CWE-23" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-10T00:29:00Z",
    "nvd_published_at" : "2026-02-09T23:16:06Z"
  }
}