How severe is GHSA-hr7j-63v7-vj7g?

No CVSS score has been assigned to GHSA-hr7j-63v7-vj7g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hr7j-63v7-vj7g?

GHSA-hr7j-63v7-vj7g affects the following packages: github.com/pterodactyl/wings (Go), pterodactyl/panel (Packagist). Ecosystems affected: Go, Packagist.

How do I fix GHSA-hr7j-63v7-vj7g?

Update github.com/pterodactyl/wings to 1.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hr7j-63v7-vj7g is resolved across your whole dependency graph.

How do I detect GHSA-hr7j-63v7-vj7g in my Go, Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pterodactyl/wings. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hr7j-63v7-vj7g if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hr7j-63v7-vj7g?

O3 pinpoints whether GHSA-hr7j-63v7-vj7g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hr7j-63v7-vj7g actively exploited in the wild?

No public exploit code has been indexed for GHSA-hr7j-63v7-vj7g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-hr7j-63v7-vj7g published, and has it been updated?

GHSA-hr7j-63v7-vj7g was published on February 17, 2026 and was last updated on February 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go🐘 Packagist

GHSA-hr7j-63v7-vj7g

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

Also known asGO-2026-4497

Published

Feb 17, 2026

Updated

Feb 23, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐹github.com/pterodactyl/wings🐘pterodactyl/panel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go, Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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 active SFTP sessions are not tracked or forcefully terminated on credential revocation events. This effectively prevents administrators from responding to credential compromise incidents in real time.

PoC

Scenario 1: Account deletion

Create a user with SFTP access to a server.
Connect to the server via SFTP using any SFTP client (e.g. sftp, FileZilla).
Keep the SFTP session open and active.
Delete the user account from the Pterodactyl Panel.
Continue performing file operations through the already-established SFTP connection.

Result: The SFTP session remains active and usable despite the user account being deleted.

Scenario 2: Password change

Create a user with SFTP access to a server.
Establish an active SFTP connection.
Change the user's password (including via administrator panel).
Continue performing file operations using the existing SFTP connection.

Result: The SFTP session remains active and usable even after the password has been changed.

Impact

This issue prevents immediate revocation of compromised credentials. Vulnerability type: Access control / session invalidation issue

Impacted parties:

Server administrators
Hosting providers using Pterodactyl Panel

Security impact:

Deleted users may retain filesystem access longer than intended, which can lead to:

Unauthorized data access
Data modification or deletion
Compliance and security policy violations

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/pterodactyl/wings`	all versions	1.12.1
🐘Packagist	`pterodactyl/panel`	all versions	1.12.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pterodactyl/wings. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/pterodactyl/wings to 1.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hr7j-63v7-vj7g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hr7j-63v7-vj7g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hr7j-63v7-vj7g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 pass

O3 Security · Impact-Aware SCA

Is GHSA-hr7j-63v7-vj7g in your dependencies?

O3 detects GHSA-hr7j-63v7-vj7g across Go, Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works