How severe is GHSA-c869-jx4c-q5fc?

No CVSS score has been assigned to GHSA-c869-jx4c-q5fc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c869-jx4c-q5fc?

GHSA-c869-jx4c-q5fc affects the following packages: fuxa-server (npm). Ecosystems affected: npm.

How do I fix GHSA-c869-jx4c-q5fc?

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

How do I detect GHSA-c869-jx4c-q5fc 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-c869-jx4c-q5fc 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-c869-jx4c-q5fc actively exploited in the wild?

No public exploit code has been indexed for GHSA-c869-jx4c-q5fc 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-c869-jx4c-q5fc?

GHSA-c869-jx4c-q5fc has an EPSS (Exploit Prediction Scoring System) score of 12.5%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-c869-jx4c-q5fc?

GHSA-c869-jx4c-q5fc is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-c869-jx4c-q5fc published, and has it been updated?

GHSA-c869-jx4c-q5fc 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 Arbitrary Scheduler WriteGHSA-c869-jx4c-q5fc

Fix: frangoteam/FUXA#2174

GHSA-c869-jx4c-q5fc is a CWE-862 vulnerability in fuxa-server. EPSS puts its 30-day exploitation probability at 12.5% (96th percentile). A fix is available for fuxa-server — see the affected versions and patch details below.

Also known asCVE-2026-25939

Published

Feb 10, 2026

Updated

Feb 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 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-c869-jx4c-q5fc.

EPSS Exploitation Probability

via FIRST.org ↗

12.5%probability of exploitation in next 30 days

Moderate Risk-0.18%

Lower risk than most CVEs96th percentile — riskier than 96% 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

26downloads / week

Description

Summary

An authorization bypass vulnerability in the FUXA allows an unauthenticated, remote attacker to create and modify arbitrary schedulers, exposing connected ICS/SCADA environments to follow-on actions. This vulnerability 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, including those with runtime.settings.secureEnabled set to true.

Exploitation allows an unauthenticated, remote attacker to automatically authenticate as guest and create, modify or delete schedules. These schedules can be configured to trigger immediately or cyclically, forcing connected devices to specific states or values, or executing existing scripts on the server.

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-c869-jx4c-q5fc 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 An authorization bypass vulnerability in the FUXA allows an unauthenticated, remote attacker to create and modify arbitrary schedulers, exposing connected ICS/SCADA environments to follow-on actions. This vulnerability 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, including those with `runtime.settings.secureEnabled` set to `true`. Exploitation allows an unauthenticated, remote attacker to automatically authenticate as guest and create, modify or delete schedules. These schedules can be co

O3 Security · Impact-Aware SCA

Is GHSA-c869-jx4c-q5fc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works