Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-67443 – Unauthenticated RCE via Node-RED Authorization Bypass – FUXA <= 1.3.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-67443 is a critical missing-authorization vulnerability (CWE-862) in FUXA, a web-based SCADA/HMI/dashboard platform, affecting versions up to and including 1.3.2. An unauthenticated attacker can obtain a signed guest JWT and use it to reach the Node-RED admin interface embedded in FUXA, ultimately achieving remote code execution as the FUXA service user. The issue carries a CVSS score of 9.2 (Critical).

Technical details

  • Root cause: the allowDashboard authorization gate for the /nodered route calls authJwt.verify() to check only the JWT signature, without inspecting the decoded token claims (e.g., via available helpers like isGuestUser() or haveAdminPermission()).
  • The unauthenticated POST /api/heartbeat endpoint issues a validly-signed guest JWT, which passes the flawed authorization gate.
  • Node-RED’s redSettings lacks adminAuth configuration, so once the gate is passed the full Node-RED admin API and flow editor are exposed.
  • fuxa.runScript() lacks the authorization checks present on the equivalent /api/runscript REST endpoint.
  • Trigger conditions: exploitation requires nodeRedEnabled=true, secureEnabled=true, and nodeRedAuthMode="secure".
  • Attack vector: network, no authentication or user interaction required.
  • Impact: an attacker can deploy malicious Node-RED function/execute-script nodes to run arbitrary code within the FUXA server process, tamper with security configuration, corrupt or delete the underlying database, manipulate HMI/device/alarm configuration, and in Docker deployments with persistent volumes potentially compromise the host.

Affected software

  • FUXA (frangoteam) versions <= 1.3.2, when Node-RED integration is enabled in secure mode.

Severity

  • CVSS v4.0 Base Score: 9.2 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: upgrade to FUXA version 1.3.3 or later, which fixes the authorization gate.
  • If patching is not immediately possible: disable the Node-RED integration (nodeRedEnabled=false) or restrict network access to the FUXA management interface to trusted hosts only, and avoid enabling nodeRedUnsafeModules, which grants deployed nodes child_process and net module access.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Loaded script: fuxa-editor.min.js
  • Page title: FUXA

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge