# CVE-2026-107854: Jexactyl: Free-billing order endpoint renews and unsuspends arbitrary servers by ID (missing ownership check)

> Authenticated users can renew or unsuspend arbitrary game servers belonging to other tenants due to missing ownership checks in the billing endpoint.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-9xwv-p7r5-5h5p

## What is CVE-2026-107854?

CVE-2026-107854 is a medium-severity missing authorization vulnerability in Jexactyl, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jexactyl is a customisable game management panel and billing system. From 4.0.0 until 4.0.5, the POST /api/client/billing/free/process endpoint accepts a client-controlled server_id and loads the server without restricting the lookup to servers owned by the authenticated account. On installations with billing enabled, an authenticated user can renew or unsuspend another tenant's billable server when its renewal_date is non-null and more than seven days away, even without a subuser relationship to that server. This issue is fixed in version 4.0.5.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-107854 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107854 is a medium-severity missing authorization vulnerability in Jexactyl, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107854 in the wild and no public exploit code.

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

## Sources

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

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