How many CVEs have patched getCurrentTokenUser?

3 published CVEs changed getCurrentTokenUser in frangoteam/FUXA, in 2 distinct patches totalling 66 changed lines, between 2026 and 2026.

What is the latest CVE that changed getCurrentTokenUser?

CVE-2026-65984 (FUXA: JWT lifecycle flaws allow deleted or demoted users to retain privileged sessions), published 2026-08-18, changed lines 289 to 310 of server/api/index.js.

How does getCurrentTokenUser compare to the rest of frangoteam/FUXA?

frangoteam/FUXA has 18 CVEs with a located fix in total; 3 of them changed getCurrentTokenUser.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

frangoteam/FUXA

Function

getCurrentTokenUser

Name: getCurrentTokenUser in frangoteam/FUXA: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

server/api/index.js

Last patched August 18, 2026

3

CVEs

That changed this function

2

Distinct patches

Backports counted once

66

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

getCurrentTokenUser in frangoteam/FUXA was changed by 3 published CVE fixes in 2026, in 2 distinct patches that added or removed 66 lines in total.

frangoteam/FUXA has 18 CVEs with a located fix in total, so 17% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed getCurrentTokenUser, newest first, with the lines each fix touched.

FUXA: JWT lifecycle flaws allow deleted or demoted users to retain privileged sessions
CVE-2026-65984 · lines 289–310 · +22 −0
High · CVSS 7.5
EPSS 0.5%2026-08-18
FUXA: SSRF hardening for `device-webapi-request`
CVE-2026-65985 · lines 289–310 · +22 −0
Medium · CVSS 6.0
EPSS 0.5%2026-08-18
FUXA: Unauthenticated Socket.IO read events
CVE-2026-67440 · lines 289–310 · +22 −0
Medium · CVSS 6.9
EPSS 0.5%2026-08-18

Get an alert when the next CVE fix lands in frangoteam/FUXA, with the patched functions.

Monitor FUXA CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in frangoteam/FUXA changed by the most CVE fixes.

init8 CVEs · server/api/index.js init5 CVEs · server/runtime/index.js mountNodeRedIfInstalled4 CVEs · server/integrations/node-red/index.js verifyGroups3 CVEs · server/api/index.js setNewToken3 CVEs · client/src/app/_services/auth.service.ts buildRefreshToken3 CVEs · server/api/auth/index.js

All patched functions in frangoteam/FUXA

Frequently asked questions

Common questions about CVE fixes to getCurrentTokenUser.

How many CVEs have patched getCurrentTokenUser?: 3 published CVEs changed getCurrentTokenUser in frangoteam/FUXA, in 2 distinct patches totalling 66 changed lines, between 2026 and 2026.
What is the latest CVE that changed getCurrentTokenUser?: CVE-2026-65984 (FUXA: JWT lifecycle flaws allow deleted or demoted users to retain privileged sessions), published 2026-08-18, changed lines 289 to 310 of server/api/index.js.
How does getCurrentTokenUser compare to the rest of frangoteam/FUXA?: frangoteam/FUXA has 18 CVEs with a located fix in total; 3 of them changed getCurrentTokenUser.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track frangoteam/FUXA CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing