Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.9

TShock Security Escalation Exploit

GHSA-hvm9-wc8j-mgrc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tshock 5.2.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • NuGet tshock

    Affected
    >= 4.3.21, < 5.2.1
    Fixed in
    5.2.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.9 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:H/SA:H · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact An issue with the way OTAPI manages client connections results in stale UUIDs remaining on RemoteClient instances after a player disconnects. Because of this, if the following conditions are met a player may assume the login state of a previously connected player: 1. The server has UUID login enabled 2. An authenticated player disconnects 3. A subsequent player connects with a modified client that does not send the ClientUUID#68 packet during connection 4. The server assigns the same RemoteClient object that belonged to the originally authenticated player to the newly connected player Patches TShock 5.2.1 hotfixes this issue. A more robust fix will be made to OTAPI itself. Workarounds Implement a RemoteClient reset event handler in a plugin like so:

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-hvm9-wc8j-mgrc

Agent brief

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

# Patch Next advisory brief: GHSA-hvm9-wc8j-mgrc

Advisory: TShock Security Escalation Exploit
IDs: GHSA-hvm9-wc8j-mgrc
Record: https://patchnext.com/advisories/ghsa-hvm9-wc8j-mgrc (revision 1, source checked 26 Oct 2026, 17:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tshock 5.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet tshock: affected >= 4.3.21, < 5.2.1; fixed in 5.2.1

## Suggested inspection (read-only)
- NuGet tshock: 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 tshock.
- 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-hvm9-wc8j-mgrc (GitHub-reviewed advisory GHSA-hvm9-wc8j-mgrc lists affected ranges: NuGet tshock >=4.3.21 <5.2.1)

Commands are suggestions: review each one before running it.

Loading voting…