PocketMine-MP versions before 5.39.2 fail to validate entity despawn state when processing attack packets from clients. Attackers can exploit a race condition by attacking a disconnecting player to trigger multiple death handlers, causing inventory items and experience to drop multiple times for duplication.
CVE-2026-86203
Score 3.7 from GitHub Security Advisory published 2026-09-09. a secondary CVSS source baseline 3.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(high)
- EG Risk
- 17(Track)EG Risk 17/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity37% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
September 9, 2026
Last Modified
September 10, 2026
References (3)
- disclosure@vulncheckhttps://github.com/pmmp/PocketMine-MP/commit/c0719b76b18f2508143134e79bc9f1aa39109683
- disclosure@vulncheckhttps://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-f9jp-856v-8642
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/pocketmine-mp-before-5.39.2-item-duplication-via-despawn-state
Vendor Advisories for CVE-2026-86203(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pocketmine/pocketmine-mp | 3.0.0 ... 5.9.0 (377 versions) | 5.39.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 21:14 UTCEG score recompute
- 2026-09-16 21:14 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-13 18:00 UTCEG score recompute
- 2026-09-13 18:00 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 15:22 UTCEG score recompute
- 2026-09-10 15:22 UTCGHSA enrichment
- 2026-09-10 15:00 UTCEG score recompute
- 2026-09-10 15:00 UTCGHSA enrichment
- 2026-09-09 20:41 UTCEG score recompute
- 2026-09-09 20:41 UTCGHSA enrichment
- 2026-09-09 14:27 UTCEG score recompute
- 2026-09-09 13:46 UTCEG score recompute
- 2026-09-09 13:44 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-86203?
When was CVE-2026-86203 disclosed?
Is CVE-2026-86203 actively exploited?
What is the CVSS score of CVE-2026-86203?
How do I remediate CVE-2026-86203?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-86203
Is Your Infrastructure Affected by CVE-2026-86203?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.