Is pocketmine/pocketmine-mp vulnerable?

Composer pocketmine/pocketmine-mp has 30 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

30advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2024-58381PocketMine-MP server crash with certain invalid JSON payloads in `LoginPacket` due to dependency vulnerability (3rd time)high7.5<5.11.15.11.1
CVE-2022-51015Unchecked validity of Facing values in PlayerActionPackethigh7.5<4.0.64.0.6
CVE-2026-86200PocketMine-MP has LogDoS by many junk properties in client data JWT in LoginPacketmedium0.0<5.42.15.42.1
CVE-2022-51017Uncapped length of skin data fields submitted by playershigh7.5<3.26.5 or >=4.0.0 and <4.0.53.26.5, 4.0.5
CVE-2023-54393PocketMine-MP vulnerable to server crash with certain invalid JSON payloads in `LoginPacket` due to vulnerable dependencyhigh7.5<4.20.5 or >=4.21.0 and <4.21.14.20.5, 4.21.1
CVE-2022-51009PocketMine-MP invalid skin geometry JSON data leading to server crashhigh7.5<4.7.24.7.2
CVE-2023-54390PocketMine-MP server crash with certain invalid JSON payloads in `LoginPacket` due to dependency vulnerability (again)high7.5>=5.0.0 and <5.3.1 or <4.23.15.3.1, 4.23.1
CVE-2026-86201PocketMine-MP: LogDoS by large complex unknown property logging in clientData in LoginPackethigh7.5<5.41.15.41.1
CVE-2025-71418PocketMine-MP allows malicious client data to waste server resources due to lack of limits for explode()medium5.3<5.25.25.25.2
CVE-2023-54394PocketMine MP vulnerable to uncontrolled resource consumption via mismatched type of 'InventoryTransactionPacket'medium5.3<4.18.0-ALPHA24.18.0-ALPHA2
CVE-2021-48007NaN/INF in serverbound movement packets can crash clients and servershigh7.5<3.18.13.18.1
CVE-2022-51010Improperly checked IDs on itemstacks received from the client leading to server crash in PocketMine-MPhigh7.5>=4.0.0-BETA5 and <4.4.24.4.2
CVE-2022-51012Insufficient type validation in pocketmine/pocketmine-mphigh7.5<4.2.94.2.9
CVE-2022-51013Improperly checked metadata on tools/armour itemstacks received from the clienthigh7.5<4.2.44.2.4
CVE-2022-51014Unhandled exception when decoding form response JSONhigh7.5>=4.0.0 and <4.0.74.0.7
CVE-2023-54392PocketMine-MP vulnerable to server crash using badly formatted sign NBT in BlockActorDataPackethigh7.5>=4.20.0 and <4.22.3 or >=5.0.0 and <5.2.14.22.3, 5.2.1
CVE-2023-54396PocketMine-MP has improperly handled dye colour IDs in banner NBT, leading to server crashhigh7.5<4.8.14.8.1
CVE-2024-58380PocketMine-MP BookEditPacket crash when inventory slot in the packet is invalidhigh7.5<5.11.25.11.2
CVE-2020-37277Exploitable inventory component chaining in PocketMine-MPhigh0.0<3.15.43.15.4
CVE-2022-51011Denial-of-service vulnerability processing large chat messages containing many newlinesmedium5.3<4.2.104.2.10
CVE-2023-54395PocketMine-MP vulnerable to denial-of-service by sending large modal form responsesmedium5.3<4.12.54.12.5
CVE-2022-51018Book page text, count, and author/title length is not limited in PocketMine-MPmedium6.5<3.26.5 or >=4.0.0 and <4.0.53.26.5, 4.0.5
CVE-2025-71417PocketMine-MP `ResourcePackDataInfoPacket` amplification vulnerability due to lack of resource pack sequence status checkinghigh0.0<5.32.15.32.1
CVE-2026-86204PocketMine-MP: JSON decoding of unlimited size large arrays/objects in ModalFormResponse Handlinghigh0.0<5.39.25.39.2
CVE-2023-7332PocketMine-MP vulnerable to improperly checked dropped item count leading to server crashhigh7.5<4.18.14.18.1
CVE-2023-54355PocketMine-MP server crash due to incorrect EC curve used for LoginPacket identityPublicKeyhigh7.5>=5.2.0 and <5.3.15.3.1
CVE-2026-86202PocketMine-MP: Network amplification vulnerability with `ActorEventPacket`medium4.3<5.39.25.39.2
CVE-2026-86203PocketMine-MP: Player entities can still die and drop items in flaggedForDespawn statelow3.7<5.39.25.39.2
CVE-2022-51016Impersonation of other users (passing XBOX Live authentication) by theft of logins in PocketMine-MPmedium4.7>=3.0.0 and <4.0.04.0.0
CVE-2021-48006Inability to de-op players if listed in ops.txt with non-lowercase letterslow3.3<4.0.34.0.3

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.