CVE-2026-65984 FUXA: JWT lifecycle flaws allow deleted or demoted users to retain privileged sessions
Attackers with valid tokens can retain privileged access after account deletion or demotion due to flawed JWT refresh logic in FUXA.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-65984?
CVE-2026-65984 is a high-severity authentication bypass vulnerability in frangoteam FUXA, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In 1.3.2 and earlier, POST /api/refresh in server/api/auth/index.js falls back from current user data to decoded.groups, including when the user is deleted or groups is zero, and POST /api/heartbeat in server/api/index.js re-signs inbound JWT claims without validating the current database record. An attacker who possesses a previously issued privileged refresh cookie or access token can continue minting privileged JWTs after account deletion, disablement, role removal, or demotion. Continued refresh-cookie rotation can extend the stale session and preserve unauthorized access to user management, project manipulation, runtime configuration, scripts, and backdoor-account creation. This issue is fixed in version 1.3.3.
Weakness: CWE-613
Which versions are affected by CVE-2026-65984?
How do I fix CVE-2026-65984?
No fix has been published for CVE-2026-65984 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-65984 being exploited?
There is no known exploitation of CVE-2026-65984 in the wild and no public exploit code.
Sources
Also known as GHSA-rg7m-xwqc-mjw6.