CVE-2026-50191
SSO-linked account takeover in 4gaBoards allows attackers to access victim projects.
Is CVE-2026-50191 being exploited?
Not confirmed. CVE-2026-50191 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-50191?
CVE-2026-50191 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50191?
Yes. A fix has been recorded for CVE-2026-50191. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50191 affect?
CVE-2026-50191 affects 4gaBoards versions prior to 3.3.8, /api/register, /api/access-tokens, SSO helper modules (Google/GitHub/Microsoft/OIDC). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50191?
Upgrade to 4gaBoards 3.3.8; disable local+SSO registration combos until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can create unverified local account with a victim email, authenticate, and retain access after victim's SSO login, exfiltrating projects, data, and permissions.
Immediate action required
- affected< 3.3.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.