CVE-2026-65984Network attack vector

Privileged session retention via stale JWT claims

Published Aug 18, 2026 · Updated Aug 19, 2026

Improper session expiration in Frangoteam FUXA 1.3.2 and earlier allows attackers to retain privileged access via stale JWT renewal. In server/api/auth/index.js, POST /api/refresh rebuilds user state with database data or decoded.groups, so deleted accounts and groups=0 fall back to claims from the old token; in server/api/index.js, POST /api/heartbeat re-signs inbound JWT claims without reloading the current database record. Reachability requires secureEnabled=true and possession of a previously issued privileged refresh cookie or access token, after which deletion, disablement, or role demotion no longer revokes access to administrative APIs, project state, runtime configuration, scripts, or backdoor-account creation.

CVSS severity7.5
High
EPSS probability0.47%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper session expiration in Frangoteam FUXA 1.3.2 and earlier allows attackers to retain privileged access via stale JWT renewal. In server/api/auth/index.js, POST /api/refresh rebuilds user state with database data or decoded.groups, so deleted accounts and groups=0 fall back to claims from the old token; in server/api/index.js, POST /api/heartbeat re-signs inbound JWT claims without reloading the current database record. Reachability requires secureEnabled=true and possession of a previously issued privileged refresh cookie or access token, after which deletion, disablement, or role demotion no longer revokes access to administrative APIs, project state, runtime configuration, scripts, or backdoor-account creation.

The record

CVE
CVE-2026-65984
Published
Aug 18, 2026
Updated
Aug 19, 2026
Vendor
Frangoteam
Product
FUXA
Classifications
CWE-613, T1550
Attack vector
network
Privileges
admin

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.3.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesadmin

What is affected?

Frangoteam · FUXAversion=< 1.3.3

Published CVSS scores

7.5GitHub, Inc.CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-613Insufficient Session Expiration
T1550Use Alternate Authentication Material

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo