Quick answers
- Is CVE-2026-67443 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67443 being exploited in the wild.
- How severe is CVE-2026-67443?
- Informational severity, with a CVSS score of 8.6, published 18 August 2026.
- Which products and versions are affected?
- FUXA Team FUXA 1.3.2 and earlier.
- Is there a fix for CVE-2026-67443?
- A patch was published on 2026-06-14: Fix released in version 1.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67443 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-67443?
- Check whether anything you run is named in the advisory. 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.
Technical details
The vulnerability is an authentication bypass in the allowDashboard authorization gate for the /nodered endpoint in server/integrations/node-red/index.js. The authJwt.verify function validates JWT signatures but does not inspect the decoded token's identity claims. An attacker can obtain a signed guest token from the unauthenticated POST /api/heartbeat endpoint and reuse it to access the Node-RED RED.httpAdmin editor and flow deployment API. When nodeRedEnabled, secureEnabled, and nodeRedAuthMode=secure are all true, the missing second-layer authorization allows the attacker to deploy function nodes and invoke fuxa.runScript and runtime.scriptsMgr.runScript without further authentication. If nodeRedUnsafeModules is enabled, the attacker can execute arbitrary operating system commands. The fix was released in version 1.3.3.
Affected products
- FUXA Team FUXA 1.3.2 and earlier
Timeline
- 2026-08-18: disclosed
- 2026-06-14: patched: Fix released in version 1.3.3