# CVE-2026-77915: rConfig Core 8.0.0 < 8.2.10 Unauthorized Admin Registration via web.php

> Unauthenticated attackers can register admin accounts due to a routing error, gaining full access to device credentials and user data.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-3xhw-7rxv-vwc7, GHSA-w3hx-9cxg-5ccr

## What is CVE-2026-77915?

CVE-2026-77915 is a critical authentication bypass vulnerability in rconfig, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

rConfig Core 8.0.0 before 8.2.10 contains an authentication bypass vulnerability that allows unauthenticated attackers to self-register accounts with full Administrator privileges due to a duplicate bare Auth::routes() call in routes/web.php that re-enables the POST /register route after it was explicitly disabled. Attackers can register a new account that is immediately authenticated with Admin-level access because the registration controller does not assign a role and the users.role column defaults to Admin, enabling access to stored device credentials, user data, and API token issuance.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2026-77915 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77915 is a critical authentication bypass vulnerability in rconfig, published on 24 Aug 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-77915 in the wild and no public exploit code.

Affected product: rconfig. 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-77915/ (Markdown: https://insights.sbomify.com/CVE-2026-77915/index.md)
```

## Sources

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

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