NaN/INF in serverbound movement packets can crash clients and servers

Exploitation

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

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact A malicious client may send a MovePlayerPacket to the server whose position or rotation contains NaN or INF. Since neither the server nor vanilla client handles this properly, a number of interesting side effects come into play. - The server may crash in various ways if this exploit is used, because some mathematical operations on NaN/INF generate PHP warnings, which are converted into exceptions. - Clients may not be able to see other clients who have a NaN/INF rotation. - Clients may also crash in such cases. Patches A patch for this was included in the 3.18.1 release: https://github.com/pmmp/PocketMine-MP/commit/fb20bb38327b4c08ee3976640cd0dd547388a638 Workarounds Workarounds could be implemented as plugins using DataPacketReceiveEvent to block any inbound movement packets containing bogus values. For more information If you have any questions or comments about this advisory: - Open an issue in pmmp/PocketMine-MP - Email us at team@pmmp.io

Published by the source

18 Mar 2022, 17:54 UTC

Last modified by the source

9 Jan 2023, 05:04 UTC

Source last checked

26 Oct 2026, 13:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fm35-jgg3-3grx

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

# Patch Next advisory brief: GHSA-fm35-jgg3-3grx

Advisory: NaN/INF in serverbound movement packets can crash clients and servers
IDs: GHSA-fm35-jgg3-3grx
Record: https://patchnext.com/advisories/ghsa-fm35-jgg3-3grx (revision 1, source checked 26 Oct 2026, 13:56 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: pocketmine/pocketmine-mp 3.18.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pocketmine/pocketmine-mp: affected <= 3.18.0; fixed in 3.18.1

## Suggested inspection (read-only)
- Packagist pocketmine/pocketmine-mp: 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 pocketmine/pocketmine-mp.
- 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-fm35-jgg3-3grx (GitHub-reviewed advisory GHSA-fm35-jgg3-3grx lists affected ranges: Packagist pocketmine/pocketmine-mp >=0 <=3.18.0)

Commands are suggestions: review each one before running it.