Quick answers
- Is CVE-2026-86203 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86203 being exploited in the wild.
- How severe is CVE-2026-86203?
- Low severity, with a CVSS score of 3.7, published 9 September 2026.
- Which products and versions are affected?
- pocketmine/pocketmine-mp (Packagist) ECOSYSTEM:introduced=0,fixed=5.39.2.
- Is there a fix for CVE-2026-86203?
- Yes. pocketmine/pocketmine-mp (Packagist): upgrade to 5.39.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86203 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86203?
- Check whether you run pocketmine/pocketmine-mp (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pocketmine/pocketmine-mp (Packagist): upgrade to 5.39.2 or later
composer require pocketmine/pocketmine-mp:^5.39.2
Technical details
The vulnerability is a race condition in entity state validation (CWE-664: Improper Control of a Resource Through its Lifetime). When a player disconnects or dies, the entity is flagged for despawn but remains in the World entity table. If an attack packet from another client arrives during a narrow timing window, the handler calls World.getEntity() without checking the flagged-for-despawn state, allowing the death handler to execute multiple times. Attack vector is network-based (another player sends attack packets) with high complexity (precise timing required) and no authentication required. An attacker can duplicate items by timing an attack on a disconnecting victim. The vulnerability was patched in version 5.39.2.
Affected products
- PocketMine PocketMine-MP before 5.39.2
Identifiers
- CVE-2026-86203
- GHSA-f9jp-856v-8642
Timeline
- 2026-04-04: disclosed
- 2026-05-09: patched: Fixed in version 5.39.2