Vulnerability in pterodactyl/panel (CVE-2026-35202)
Summary
Vulnerability in pterodactyl/panel (CVE-2026-35202). Risk of unauthorized operations or information disclosure. Exploitable via DatabaseController.php. Mitigation: upgrade to 1.12.3 or later.
Original description
The description as published by the source.
Pterodactyl is a free, open-source game server management panel. Prior to version 1.12.3, the Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything. Version 1.12.3 patches the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35202 has been found in pterodactyl/panel.
Attackers can target a specific entry point like DatabaseController.php over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pterodactyl/panel to 1.12.3 or later.
If unsure, ask your IT team or search "pterodactyl/panel CVE-2026-35202" on the vendor's site.
CVE-2026-35202 (pterodactyl/panel) — CWE-367
Attack surface: DatabaseController.php / DeployServerDatabaseService
Patched: 1.12.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-367) exists in pterodactyl/panel. Attackers reach the vulnerable code path via DatabaseController.php.
Check the vendor advisory for the affected versions of pterodactyl/panel. Attack surface: DatabaseController.php / DeployServerDatabaseService.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.12.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pterodactyl/panel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pterodactyl/panel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pterodactyl/panelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pterodactyl/panel to 1.12.3ステージング環境で 1.12.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com