How severe is GHSA-v4p5-w6r3-2x4f?

No CVSS score has been assigned to GHSA-v4p5-w6r3-2x4f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v4p5-w6r3-2x4f?

GHSA-v4p5-w6r3-2x4f affects the following packages: fuxa-server (npm). Ecosystems affected: npm.

How do I fix GHSA-v4p5-w6r3-2x4f?

Update fuxa-server to 1.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v4p5-w6r3-2x4f is resolved across your whole dependency graph.

How do I detect GHSA-v4p5-w6r3-2x4f in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fuxa-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-v4p5-w6r3-2x4f if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-v4p5-w6r3-2x4f actively exploited in the wild?

No public exploit code has been indexed for GHSA-v4p5-w6r3-2x4f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-v4p5-w6r3-2x4f?

GHSA-v4p5-w6r3-2x4f has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v4p5-w6r3-2x4f?

GHSA-v4p5-w6r3-2x4f is classified as CWE-290 (CWE-290), Missing Authentication (CWE-306). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v4p5-w6r3-2x4f published, and has it been updated?

GHSA-v4p5-w6r3-2x4f was published on February 10, 2026 and was last updated on February 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

FUXA Unauthenticated Remote Code Execution in Node-RED IntegrationGHSA-v4p5-w6r3-2x4f

Fix: frangoteam/FUXA@5e7679b

GHSA-v4p5-w6r3-2x4f is a CWE-290 vulnerability in fuxa-server. A fix is available for fuxa-server — see the affected versions and patch details below.

Also known asCVE-2026-25938

Published

Feb 10, 2026

Updated

Feb 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v4p5-w6r3-2x4f.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk-0.28%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

fuxa-servernpm

39downloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`fuxa-server`	≥ 1.2.8&&< 1.2.11	1.2.11`npm install fuxa-server@1.2.11`

Affected Products

1 product · 1 configurations

Application

fuxafrangoteam

≥ 1.2.8 && < 1.2.11

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fuxa-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fuxa-server to 1.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v4p5-w6r3-2x4f is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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, g

O3 Security · Impact-Aware SCA

Is GHSA-v4p5-w6r3-2x4f in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works