# CVE-2026-86177: Pterodactyl Panel before 1.14.1 Privilege Escalation via Schedule Tasks

> Subusers can execute arbitrary console commands and control server state by bypassing permission checks in scheduled task creation.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 5 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-v29m-2pj3-6rhv

## What is CVE-2026-86177?

CVE-2026-86177 is a high-severity missing authorization vulnerability in pterodactyl panel, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pterodactyl Panel before 1.14.1 fails to validate action-specific permissions in scheduled task creation, allowing subusers with only schedule.update permission to execute arbitrary console commands. Attackers can create and immediately trigger scheduled tasks that run game-server console commands, control server power state, or create backups without proper authorization checks.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-86177 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86177 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86177 is a high-severity missing authorization vulnerability in pterodactyl panel, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86177 exists.

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

## Sources

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

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