CVE-2026-25938: FUXA Unauthenticated Remote Code Execution in Node-RED Integration

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 1.5%, percentile 74: FIRST’s model estimates a 1.5% chance of exploitation activity in the next 30 days, higher than 74% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes fuxa-server (npm) >= 1.2.8, < 1.2.11, fixed in 1.2.11. Check your lockfile, including transitive dependencies.

What it is

FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. From 1.2.8 through 1.2.10, an authentication bypass vulnerability in FUXA allows an unauthenticated, remote attacker to execute arbitrary code on the server when the Node-RED plugin is enabled. This has been patched in FUXA version 1.2.11.

From the GitHub advisory

Summary

Description An authentication bypass vulnerability in FUXA allows an unauthenticated, remote attacker to execute arbitrary code on the server when the Node-RED plugin is enabled. This affects FUXA version 1.2.8 through version 1.2.10. This has been patched in FUXA version 1.2.11.

Impact This affects all deployments with the Node-RED plugin enabled, including those with runtime.settings.secureEnabled set to true.

Exploitation allows an unauthenticated, remote attacker to send a specially crafted request to the /nodered/flows endpoint to bypass authentication checks, granting the attacker administrative access to the Node-RED deployment API. By submitting a malicious flow configuration, an attacker can execute arbitrary code in the context of the FUXA service. Depending on deployment configuration and permissions, this may lead to full system compromise and could further expose connected ICS/SCADA environments to follow-on actions.

Patches This issue has been patched in FUXA version 1.2.11. Users are strongly encouraged to update to the latest available release.

Weakness type: CWE-290, CWE-306.

Product: fuxa-server (npm) · Assigned by: GitHub_M · Published: 2026-02-09

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: present (depends on deployment conditions)
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 1.48% probability of exploitation activity in the next 30 days; percentile 74.

Timeline

• 2026-02-09 — CVE record published by GitHub_M
• 2026-02-10 — GitHub-reviewed advisory GHSA-v4p5-w6r3-2x4f published (critical)
• 2026-02-11 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-v4p5-w6r3-2x4f github.com
2. CVE.org record CVE-2026-25938 cve.org
3. NVD entry CVE-2026-25938 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com
3. github.com github.com

Critical npm advisories · Today’s Security Digest