Pterodactyl Panel's SFTP sessions remain active after user account deletion or password change

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.5 · CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Deleting a user account with SFTP access or changing the user's password does not immediately terminate existing SFTP sessions, allowing continued filesystem access after credentials are revoked. This can result in unintended and unauthorized access to server files even after administrators believe access has been fully invalidated. Details When a user with SFTP access is deleted from the Pterodactyl Panel or when the user's password is changed while one or more SFTP connections are active, those existing connections remain fully functional. Neither account deletion nor password change invalidates the authentication state of already-established SFTP sessions. As a result, the active SFTP connection pool continues to allow read and write operations until the client disconnects or the session times out. This behavior occurs even when the password is changed by an administrator through the panel, meaning credential rotation does not revoke active access. This suggests that…

Published by the source

17 Feb 2026, 17:15 UTC

Last modified by the source

17 Feb 2026, 17:15 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hr7j-63v7-vj7g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-hr7j-63v7-vj7g

Advisory: Pterodactyl Panel's SFTP sessions remain active after user account deletion or password change
IDs: GHSA-hr7j-63v7-vj7g
Record: https://patchnext.com/advisories/ghsa-hr7j-63v7-vj7g (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pterodactyl/panel 1.12.1; github.com/pterodactyl/wings 1.12.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pterodactyl/panel: affected < 1.12.1; fixed in 1.12.1
- Go github.com/pterodactyl/wings: affected < 1.12.1; fixed in 1.12.1

## Suggested inspection (read-only)
- Packagist pterodactyl/panel: check the installed version with your package manager.
- Go github.com/pterodactyl/wings: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pterodactyl/panel, github.com/pterodactyl/wings.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hr7j-63v7-vj7g (GitHub-reviewed advisory GHSA-hr7j-63v7-vj7g lists affected ranges: Packagist pterodactyl/panel >=0 =0 <1.12.1)

Commands are suggestions: review each one before running it.