LiveActive security incident?Get immediate response
CVE Record

CVE-2026-67443: FUXA: Unauthenticated guest JWT bypasses Node-RED secure-mode authorization gate (Remote Script Execution)

FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In 1.3.2 and earlier, the allowDashboard authorization gate in server/integrations/node-red/index.js calls authJwt.verify for /nodered without inspecting the decoded identity. When nodeRedEnabled is true, secureEnabled is true, and nodeRedAuthMode is secure, a remote unauthenticated attacker can obtain a signed guest token from POST /api/heartbeat and use it to access the RED.httpAdmin editor and flow deployment API. Because the Node-RED configuration has no second adminAuth gate, the attacker can deploy function nodes or invoke fuxa.runScript and runtime.scriptsMgr.runScript, gaining control of FUXA project data, configuration, scripts, filesystem-capable runtime helpers, and potentially operating-system commands when nodeRedUnsafeModules is enabled. This issue is fixed in version 1.3.3.

CriticalCVSS 9.2Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A remote attacker without an account could use a legitimate guest token to enter FUXA’s Node-RED administration interface under specific configurations. From there, they could alter automation flows, scripts, project data, and configuration, potentially reaching operating-system commands. FUXA versions before 1.3.3 are affected.

Executive priority

Treat affected, reachable installations as an immediate remediation priority, especially where FUXA connects to SCADA, HMI, or operational environments. Upgrade promptly and investigate suspicious Node-RED or script changes. Current sources do not prove exploitation in the wild, but the potential compromise of monitoring, configuration, and host-level capabilities supports critical handling.

Technical view

The /nodered authorization gate verifies a signed JWT but does not confirm that its decoded identity is authorized. A guest JWT obtainable through /api/heartbeat therefore passes the gate when Node-RED and secure mode are configured as described. The exposed editor and deployment API enable remote script execution. This is CWE-862 with CVSS 4.0 score 9.2.

Likely exposure

Exposure requires FUXA before 1.3.3 with nodeRedEnabled and secureEnabled enabled, nodeRedAuthMode set to secure, and /nodered remotely reachable. Impact may expand to operating-system command execution when nodeRedUnsafeModules is enabled. Deployments without these conditions are not established as exploitable by the supplied evidence.

Exploitation context

The vulnerability is remotely reachable, needs no privileges or user interaction, and requires particular configuration conditions. The supplied record states that it is not in KEV, and no cited source establishes active exploitation. Public disclosure and a vendor patch nevertheless make prompt remediation appropriate.

Researcher notes

The authorization failure is identity-blind token validation: signature validity is treated as authorization. The stated attack path depends on guest-token availability and the named Node-RED configuration. The absence of a secondary adminAuth check enables editor and deployment access. Review the vendor commit and pull request for the exact authorization change; avoid assuming other FUXA routes are affected.

Mitigation direction

  • Upgrade FUXA to version 1.3.3 or later.
  • Prioritize internet-accessible or operational-technology deployments meeting the vulnerable configuration conditions.
  • Until upgraded, reduce external access to FUXA and Node-RED administrative routes.
  • Consult the vendor advisory for any deployment-specific interim guidance.
  • Review whether nodeRedUnsafeModules is enabled and disable it unless operationally required.

Validation and detection

  • Inventory FUXA instances and record their installed versions.
  • Check nodeRedEnabled, secureEnabled, nodeRedAuthMode, and nodeRedUnsafeModules settings.
  • Confirm that exposed instances no longer run versions earlier than 1.3.3.
  • Review logs for unexpected guest-token issuance, /nodered access, flow deployment, or script activity.
  • Validate that Node-RED administration is inaccessible to unauthenticated or guest identities after remediation.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-67443 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.2 (4.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——GitHub_M

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2026-67443Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
frangoteamFUXA< 1.3.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.