CVE-2026-25894: FUXA unauthenticated remote code execution via hardcoded JWT secret

CVE-2026-25894 · Severity: medium · CVSS 4 · Published 2026-02-05

FUXA is a web-based industrial control system visualization tool used for process monitoring and automation in SCADA/HMI environments. When authentication is enabled but the administrator fails to configure a JWT secret, the application accepts tokens signed with a publicly known hardcoded key, allowing an unauthenticated attacker to forge valid credentials, gain full administrative access, and execute arbitrary code on the server. This poses a critical risk to industrial operations and connected control systems.

Technologies: Frangoteam FUXA, fuxa-server (npm). Vendors: Frangoteam, npm.

Quick answers

Is CVE-2026-25894 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-25894 being exploited in the wild.
How severe is CVE-2026-25894?
Medium severity, with a CVSS score of 4, published 5 February 2026.
Which products and versions are affected?
Frangoteam FUXA <= 1.2.9; fuxa-server (npm) SEMVER:introduced=0,fixed=1.2.10.
Is there a fix for CVE-2026-25894?
Yes. fuxa-server (npm): upgrade to 1.2.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-25894 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-25894?
Check whether you run Frangoteam FUXA or fuxa-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • fuxa-server (npm): upgrade to 1.2.10 or later
    npm install fuxa-server@1.2.10

Technical details

This vulnerability stems from an insecure default configuration in FUXA versions up to 1.2.9 where the JWT secret configuration option was only available via manual configuration file editing, not through the UI. When administrators enable authentication without explicitly setting a custom JWT secret, the application falls back to a hardcoded default key. An unauthenticated, remote attacker can exploit this by crafting and signing JWT tokens using the publicly known secret, completely bypassing all authentication controls. Once authenticated as an administrator, the attacker gains access to administrative APIs designed for automation and scripting, enabling arbitrary code execution in the context of the FUXA service. Depending on deployment configuration and system permissions, this can result in full system compromise and potential compromise of connected industrial control systems. The vulnerability has been patched in FUXA version 1.2.10, which enforces JWT secret configuration when enabling authentication and provides UI-based configuration options.

Affected products

  • frangoteam FUXA <= 1.2.9

Identifiers

  • CVE-2026-25894
  • GHSA-32cc-x95p-fxcg

Timeline

  • 2026-02-05: disclosed: GHSA-32cc-x95p-fxcg published
  • 2026-01-24: patched: Fix committed; patched in v1.2.10 released 2026-01-25

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.