CVE-2026-43945: FUXA Remote Code Execution via Path Manipulation & Configuration Injection

@frangoteam/fuxa Updated 27 May 2026

Summary

26/05/2026
Yes i
High
8.9

CVE-2026-43945: FUXA Vulnerable to Pre-auth RCE via Path Manipulation & Configuration Injection. Affects @frangoteam/fuxa versions >= 1.2.11, < 1.3.1. Fixed in 1.3.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

FUXA is an open-source framework designed to facilitate the integration of various IoT devices and services, particularly in industrial settings. It provides functionalities for managing data streams and automating processes. However, a critical vulnerability has been identified in version 1.3.0-2706, which exposes the system to remote code execution (RCE) attacks, even under secure configurations.

Vulnerability Detail

The vulnerability arises from a Path Confusion flaw in the authentication middleware of FUXA. The server improperly uses a substring match on the full URL, including query parameters, to determine authentication requirements. This allows an unauthenticated attacker to bypass security checks by appending specific query parameters to administrative requests, potentially leading to full remote code execution within the Node-RED environment. The impact is severe, as it grants attackers access to sensitive industrial data and control over critical systems.

How To Fix

Latest published version: 1.3.5 as of 23 Oct 2026

npm install @frangoteam/fuxa@1.3.5

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.3.1

This is the first release that contains the fix.

npm install @frangoteam/fuxa@1.3.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can modify the authentication middleware to use 'req.path' instead of 'req.originalUrl'. This change ensures that query strings are not considered in the authentication logic. The secure approach can be implemented as follows:

const pathname = req.path;
if (pathname.startsWith('/socket.io/')) return next();

Conclusion

In summary, CVE-2026-43945 represents a critical vulnerability in the FUXA framework that allows for remote code execution due to improper authentication handling. Users are strongly advised to update to the latest version to mitigate this risk and ensure the security of their systems.

See every vulnerability recorded for @frangoteam/fuxa →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 8.9, indicating a high severity level.

Yes, the vulnerability allows unauthenticated remote attackers to exploit the system.

FUXA versions prior to 1.3.1 are affected by this vulnerability.

Exploitation of this vulnerability can lead to full remote code execution, allowing attackers to manipulate industrial data and systems.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Related vulnerabilities

Recent vulnerabilities recorded for @frangoteam/fuxa.

How To Fix

Latest published version: 1.3.5 as of 23 Oct 2026

npm install @frangoteam/fuxa@1.3.5

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.3.1

This is the first release that contains the fix.

npm install @frangoteam/fuxa@1.3.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback