CVE-2022-51010

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-07. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

PocketMine-MP versions before 4.4.2 fail to properly validate item IDs received from clients in itemstack NBT data. Attackers can send crafted item IDs outside the valid range to trigger an uncaught exception that crashes the server.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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 computed
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

September 7, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Sep 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic

PocketMine-MP before 4.4.2 Server Crash via Item ID | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pocketmine-mp-before-4.4.2-server-crash-via-item-id
github Patch Available🟡 PoC Available

Improperly checked IDs on itemstacks received from the client leading to server crash · Advisory · pmmp/PocketMine-MP · GitHub

https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-fqx3-r75h-vc89
github_commit

commit 5fd685e07d61 (pmmp/PocketMine-MP)

Fix landed in pmmp/PocketMine-MP commit 5fd685e07d61 — awaiting tagged release

https://github.com/pmmp/PocketMine-MP/commit/5fd685e07d61ef670584ed11a52fd5f4b99a81a7

Vendor Advisories for CVE-2022-51010(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)
PackageVulnerable rangeFixed inDependents
pocketmine/pocketmine-mp4.0.0 ... 4.4.1 (43 versions)4.4.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 36× 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.

  1. 2026-09-18 11:38 UTCEG score recompute
  2. 2026-09-18 11:38 UTCGHSA enrichment
  3. 2026-09-17 12:23 UTCEG score recompute
  4. 2026-09-17 12:23 UTCGHSA enrichment
  5. 2026-09-16 14:05 UTCEPSS rescore
  6. 2026-09-16 13:15 UTCEG score recompute
  7. 2026-09-16 13:15 UTCGHSA enrichment
  8. 2026-09-16 05:11 UTCEPSS rescore
  9. 2026-09-15 14:04 UTCEG score recompute
  10. 2026-09-15 14:04 UTCGHSA enrichment
  11. 2026-09-15 03:07 UTCEPSS rescore
  12. 2026-09-14 14:57 UTCEG score recompute
  13. 2026-09-14 14:57 UTCGHSA enrichment
  14. 2026-09-13 16:44 UTCEPSS rescore
  15. 2026-09-13 15:50 UTCGHSA enrichment
  16. 2026-09-12 16:43 UTCEG score recompute
  17. 2026-09-12 16:43 UTCGHSA enrichment
  18. 2026-09-11 17:36 UTCEG score recompute
  19. 2026-09-11 17:36 UTCGHSA enrichment
  20. 2026-09-11 14:50 UTCEPSS rescore
  21. 2026-09-11 09:34 UTCEPSS rescore
  22. 2026-09-10 18:29 UTCEG score recompute
  23. 2026-09-10 18:28 UTCGHSA enrichment
  24. 2026-09-09 19:21 UTCEG score recompute
  25. 2026-09-09 19:21 UTCGHSA enrichment
Show 11 more
  1. 2026-09-08 21:57 UTCEPSS rescore
  2. 2026-09-08 20:13 UTCGHSA enrichment
  3. 2026-09-08 14:47 UTCEG score recompute
  4. 2026-09-08 14:47 UTCGHSA enrichment
  5. 2026-09-08 13:48 UTCEG score recompute
  6. 2026-09-08 13:48 UTCGHSA enrichment
  7. 2026-09-08 12:39 UTCEG score recompute
  8. 2026-09-08 12:38 UTCGHSA enrichment
  9. 2026-09-07 13:23 UTCEG score recompute
  10. 2026-09-07 13:04 UTCEG score recompute
  11. 2026-09-07 13:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2022-51010?
CVE-2022-51010 is a medium vulnerability published on September 7, 2026. PocketMine-MP versions before 4.4.2 fail to properly validate item IDs received from clients in itemstack NBT data. Attackers can send crafted item IDs outside the valid range to trigger an uncaught exception that crashes the server.
When was CVE-2022-51010 disclosed?
CVE-2022-51010 was first published in the National Vulnerability Database on September 7, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-51010 actively exploited?
CVE-2022-51010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.7% of all scored CVEs.
What is the CVSS score of CVE-2022-51010?
CVE-2022-51010 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2022-51010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-51010, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-51010

Explore →

Is Your Infrastructure Affected by CVE-2022-51010?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.