CVE-2025-68954: Pterodactyl does not revoke SFTP access when server is deleted or permissions reduced
Summary Pterodactyl does not revoke active SFTP connections when a user is removed from a server instance or has their permissions changes with respect to file access over SFTP. This allows a user that was already connected to SFTP to remain connected and access files even after their permissions are revoked.
Published Jan 6, 2026
Affected packages
pterodactyl/panel
- Ecosystem
- Composer (PHP)
- Affected
- < 1.12.0
- Fixed in
- 1.12.0
- Check
composer show pterodactyl/panel
github.com/pterodactyl/wings
- Ecosystem
- Go
- Affected
- < 1.12.0
- Fixed in
- 1.12.0
- Check
go list -m github.com/pterodactyl/wings
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Pterodactyl does not revoke _active_ SFTP connections when a user is removed from a server instance or has their permissions changes with respect to file access over SFTP. This allows a user that was already connected to SFTP to remain connected and access files even after their permissions are revoked.
Details
When a user opens a connection to a server using the Wings SFTP server instance the permissions are checked and returned from the authentication API call made to the Panel. However, credentials are not checked again after the initial handshake. Thus, if a user is removed from a server in the panel or have their permissions modified, those permissions are not updated in the SFTP connection.
As a result, a user that has already gained access to a server's files via the SFTP subsystem will maintain those permissions until disconnected (via Wings restart, or a manual disconnection on their end).
[!NOTE] > > This issue impacts the SFTP subsystem for server files specifically. There is no exposure of Wings private data, or any data outside of a server's local filesystem. Additionally, a user must have been _connected to SFTP at the time of their permissions being revoked_ in order for this issue to be exploited. If a user was not connected, they would not be able to connect once their permissions were reduced.
Fix
Please upgrade to [email protected] and [email protected] to resolve this issue. Patches are available via the implementation PRs, but it is recommended to apply by upgrading the entire instance.
Credited to real2two.
References
- https://github.com/pterodactyl/panel/security/advisories/GHSA-8c39-xppg-479c
- https://nvd.nist.gov/vuln/detail/CVE-2025-68954
- https://github.com/pterodactyl/panel/commit/2bd9d8baddb0e0606e4a9d5be402f48678ac88d5
- https://github.com/pterodactyl/panel/releases/tag/v1.12.0
- https://github.com/advisories/GHSA-8c39-xppg-479c
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-52855
Wings exposes node configuration secrets through egg configuration-file templating
critical9.9Jul 31, 2026CVE-2026-52856
Wings: Maliciously crafted packet during SFTP connection handshake causes denial of service
high7.5Jul 31, 2026CVE-2026-52857
Wings: Maliciously or erroneously created parsed config files can cause wings process to OOM
medium5.5Jul 31, 2026CVE-2026-54593
Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions
high8.1Jul 28, 2026CVE-2026-61609
Pterodactyl's shared global rate-limit key on login and 2FA checkpoint enables unauthenticated panel-wide authentication lockout (DoS)
high7.5Jul 28, 2026GHSA-j7f5-gfqm-pcx3
Pterodactyl Panel: Client email change endpoint allows enumeration of accounts in system
medium5.5Jun 26, 2026
