/

CVE-2026-34456

Severity:

CRITICAL RISK

(9.1)

Improper Access Control in Reviactyl Game Server Panel

CVE-2026-34456

Analyzed

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Full Account Takeover / Authentication Bypass

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A flaw in Reviactyl's OAuth authentication flow automatically linked social login accounts to existing users based solely on matching email addresses.

An attacker who can control a social identity (e.g., Google, GitHub, Discord) using a victim's email address could gain full access to the victim's Reviactyl account without knowing their password, resulting in account takeover with no prior authentication.

Affected context

The vulnerability appears in Reviactyl's web-based authentication layer where OAuth providers are used for social sign-in.

It affects deployments that:

  • Enable social login providers (Google, GitHub, Discord, etc.)
  • Automatically link incoming OAuth identities to local accounts by email
  • Do not require prior local authentication or an explicit verification step before linking a new social identity

Under these conditions, the integrity of account-bound identities depends solely on the email address asserted by the OAuth provider.

Exploit preconditions

  • Attack surface: Public web interface of the Reviactyl panel's login/registration pages.
  • Required access: Ability to authenticate to a supported social provider using an email address that matches an existing Reviactyl user's email (e.g., by registering a new social account with that address or compromising an existing social account).
  • Trigger point: Initiating the OAuth login flow with the controlled social account and completing the callback to Reviactyl.
  • Why exploitation is possible: The application trusts the email attribute from the OAuth provider as a sufficient identifier and automatically links the social identity to an existing local account without additional ownership proof, prior session, or confirmation from the rightful account owner.

Why this happens

This issue stems from improper access control and identity binding logic during OAuth account linking.

The application equates "same email address" with "same user" and automatically associates the incoming OAuth identity with the corresponding local account, effectively treating a single attribute as a strong authenticator.

This maps to CWE-284: Improper Access Control, where the system fails to enforce adequate authorization and identity verification before granting access to protected accounts.

In a secure pattern, linking a new identity factor should require an already authenticated session, a second factor, or out-of-band verification, rather than trusting a single, unverified attribute from an external provider.

Potential impact

  • Complete takeover of victim accounts, including full control over game servers and management actions.
  • Unauthorized configuration changes, such as modifying server settings, permissions, or deployments.
  • Potential data exposure for any personal or operational data stored in the panel.
  • Abuse of the victim's account to perform further attacks against infrastructure or other users.
  • Loss of audit integrity, as actions appear to originate from the compromised victim account.

General mitigation guidance

Effective mitigation usually focuses on strengthening identity binding and account linking flows:

  • Require that linking a new OAuth provider to an existing account only be allowed from a session where the user is already authenticated with their primary credential.
  • Introduce explicit user consent flows: when an OAuth login email matches an existing account, ask the user to confirm or to log in with their existing method before linking.
  • Treat email equality as a heuristic, not an authoritative proof of ownership; rely on multi-factor or step-up authentication when modifying authentication factors.
  • Disallow silent auto-linking; instead, surface a clear "link account" action in user settings with verification steps.
  • Apply least-privilege principles to identity changes, logging all account-linking events and optionally requiring administrative review in high-risk environments.

How teams detect issues like this

Organizations can detect similar flaws by focusing on authentication and account-linking logic:

  • Static analysis and code review targeting:
  • Automatic associations between external identities and local accounts based on a single attribute (e.g., email).
  • Code paths that modify authentication methods or linked identities without checking for an authenticated session.
  • Design and threat modeling reviews for OAuth/OpenID Connect flows, checking:
  • Whether new identity factors can be added or changed without strong re-authentication.
  • Whether identity linking is triggered implicitly based on data from external providers.
  • Automated tests or security checks that simulate OAuth logins with controlled accounts to verify that:
  • Existing local accounts are not silently claimed or linked.
  • Linking requires explicit user action and authenticated context.
  • Centralized logging and anomaly detection on:
  • Sudden changes in login methods for existing accounts.
  • Multiple accounts being accessed shortly after new social identities are linked.

Sources

SourceLink
github.comgithub.com/reviactyl/panel/commit/fe0c29fc62fefe354c9ab8936dfe30fdb586a896
github.comgithub.com/reviactyl/panel/releases/tag/v26.2.0-beta.5
github.comgithub.com/reviactyl/panel/security/advisories/GHSA-8mcf-rp68-xhfg

Frequently asked

questions

Yes. The attack surface is the public web login interface. As long as an attacker can complete the OAuth flow with a social provider using a matching email address, they can attempt exploitation over the network.

No. The weakness allows full account takeover based solely on controlling a social login that reports the same email address as the victim's account; no prior knowledge of the victim's password or active session is required.

Require strong, explicit verification before linking or changing authentication factors—typically enforcing that users are already authenticated with their primary credential, and potentially requiring additional confirmation (e.g., re-entering the password or a second factor) before binding a new OAuth identity.

Treat identity linking as a privileged operation: use threat modeling for all OAuth and SSO flows, avoid auto-linking based purely on attributes like email, implement explicit consent and re-authentication for account changes, and include tests and security reviews that focus specifically on account creation and linking edge cases.

Find out what's already
exploitable in your codebase.