CVE-2026-53958: RARgames 4gaBoards · Improper Authentication
Affects RARgames 4gaBoardsSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 3.3.9 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.3.9
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade 4gaBoards and rargames/4gaBoards to 3.3.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RARgames4gaBoards | Affected
| Fixed in
|
GitHubrargames/4gaBoardspkg:github/rargames/4gaBoardsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade 4gaBoards to version 3.3.9 or later, where this improper authentication vulnerability is fixed. No other mitigation is required as the fix addresses the root cause.
Description
CVE-2026-53958 is an improper authentication vulnerability in 4gaBoards prior to version 3.3.9. It allows an authenticated user to modify backend-managed single sign-on (SSO) identity attributes via a PATCH request to the user API. This flaw enables an attacker to associate a victim's SSO provider identifier with the attacker's account, causing the victim to be logged into the attacker-controlled account upon their first SSO login. The vulnerability is fixed in version 3.3.9.