Account takeover via unverified SSO linkage
Published Aug 18, 2026 · Updated Aug 19, 2026
Authentication bypass in 4ga Labs 4ga Boards before 3.3.8 allows remote attackers to take over accounts via SSO email linking. POST /api/register creates unverified local accounts for arbitrary email addresses, POST /api/access-tokens authenticates them while isVerified is false, and the get-create-one-for-github-sso.js, get-create-one-for-google-sso.js, get-create-one-for-microsoft-sso.js, and get-create-one-for-oidc-sso.js helpers bind a first SSO login to an existing account matched only by email. Exposure requires registrationEnabled, localRegistrationEnabled, and ssoRegistrationEnabled plus a configured Google, GitHub, Microsoft, or OIDC provider; the attacker retains local-password access to the victim's linked account, projects, data, and permissions.
Summary
What happened
Authentication bypass in 4ga Labs 4ga Boards before 3.3.8 allows remote attackers to take over accounts via SSO email linking. POST /api/register creates unverified local accounts for arbitrary email addresses, POST /api/access-tokens authenticates them while isVerified is false, and the get-create-one-for-github-sso.js, get-create-one-for-google-sso.js, get-create-one-for-microsoft-sso.js, and get-create-one-for-oidc-sso.js helpers bind a first SSO login to an existing account matched only by email. Exposure requires registrationEnabled, localRegistrationEnabled, and ssoRegistrationEnabled plus a configured Google, GitHub, Microsoft, or OIDC provider; the attacker retains local-password access to the victim's linked account, projects, data, and permissions.
The record
- CVE
- CVE-2026-50191
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- 4ga Labs
- Product
- 4ga Boards
- Classifications
- CWE-287, CWE-288, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=< 3.3.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- Automated Sails REPL proof of concept in GHSA-f3p6-chc6-pc77proof of concept · demonstrated
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