{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-65984 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-65984 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-65984 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-65984 in the wild and no public exploit code.\n\nAffected product: frangoteam FUXA. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-65984/ (Markdown: https://insights.sbomify.com/CVE-2026-65984/index.md)","id":"CVE-2026-65984","markdown":"https://insights.sbomify.com/CVE-2026-65984/index.md","name":"CVE-2026-65984","record":{"aliases":["GHSA-rg7m-xwqc-mjw6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SCADA HMI software","requires_auth":"high_privilege","summary":"Attackers with valid tokens can retain privileged access after account deletion or demotion due to flawed JWT refresh logic in FUXA.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"FUXA: JWT lifecycle flaws allow deleted or demoted users to retain privileged sessions","id":"CVE-2026-65984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"FUXA: SSRF hardening for `device-webapi-request`","id":"CVE-2026-65985"},"packages":[],"prev":{"headline":"Coturn: MOBILITY-TICKET session-resume authorization bypass allows cross-user TURN allocation takeover","id":"CVE-2026-65981"},"products":["FUXA"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["frangoteam"]},"summary":"Attackers with valid tokens can retain privileged access after account deletion or demotion due to flawed JWT refresh logic in FUXA.","url":"https://insights.sbomify.com/CVE-2026-65984/"}