# CVE-2026-34456: Reviactyl: OAuth account takeover via auto-linking

> Attackers can take over user accounts by linking social profiles with matching emails, bypassing password authentication in Reviactyl.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-8mcf-rp68-xhfg

## What is CVE-2026-34456?

CVE-2026-34456 is a critical authentication bypass vulnerability in reviactyl panel, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Reviactyl is an open-source game server management panel built using Laravel, React, FilamentPHP, Vite, and Go. From version 26.2.0-beta.1 to before version 26.2.0-beta.5, a vulnerability in the OAuth authentication flow allowed automatic linking of social accounts based solely on matching email addresses. An attacker could create or control a social account (e.g., Google, GitHub, Discord) using a victim’s email address and gain full access to the victim's account without knowing their password. This results in a full account takeover with no prior authentication required. This issue has been patched in version 26.2.0-beta.5.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-34456?

It affects 1 product.


Products: Reviactyl Reviactyl.

## How do I fix CVE-2026-34456?

No fix has been published for CVE-2026-34456 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34456 being exploited?

There is no known exploitation of CVE-2026-34456 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34456 and fix it if it is affected.

What it is: CVE-2026-34456 is a critical authentication bypass vulnerability in reviactyl panel, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34456 in the wild and no public exploit code.

Affected product: reviactyl panel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34456/ (Markdown: https://insights.sbomify.com/CVE-2026-34456/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34456
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34456
- OSV: https://osv.dev/vulnerability/CVE-2026-34456

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34456/
Summaries are generated and may contain mistakes; the official description above is the record.