CVE-2026-41418: RARgames 4gaBoards · Timing Side Channel
Affects RARgames 4gaBoardsSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.3.5 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.3.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Apr 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 30 Oct 2026.
What to do
Upgrade 4gaBoards and rargames/4gaBoards to 3.3.5.
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 4ga Boards to version 3.3.5 or later, where this timing side-channel vulnerability has been fixed. No other mitigation is indicated or required according to the available data.
Description
CVE-2026-41418 is a timing side-channel vulnerability in 4ga Boards versions prior to 3.3.5 that allows user enumeration via the login endpoint. The server responds significantly faster when an invalid username/email is provided compared to a valid username/email with an incorrect password, due to the bcrypt.compareSync() operation. This timing difference is easily detectable over a network with a single request. The vulnerability has a medium severity with a CVSS score of 5.3 and is fixed in version 3.3.5.