# CVE-2025-71417: PocketMine-MP before 5.32.1 Denial of Service via ResourcePackClientResponsePacket

> Authenticated attackers can cause server memory exhaustion and denial of service by sending duplicate pack UUIDs in PocketMine-MP.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-fqqv-56h5-f57g, GHSA-j79r-9x96-ppx6

## What is CVE-2025-71417?

CVE-2025-71417 is a high-severity denial of service vulnerability in pmmp PocketMine-MP, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PocketMine-MP before 5.32.1 fails to validate uniqueness of pack UUIDs in ResourcePackClientResponsePacket STATUS_SEND_PACKS handling, allowing authenticated clients to trigger duplicate pack transmissions. Attackers can send multiple copies of valid pack UUIDs in a single packet to exhaust server memory and cause denial of service.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-71417?

2 open source packages ship an affected version, including pocketmine/pocketmine-mp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pocketmine/pocketmine-mp` | Packagist | All versions | 5.32.1 |
| `pocketmine/pocketmine-mp` | Packagist | All versions | 5.32.1 |

## How do I fix CVE-2025-71417?

Upgrade pocketmine/pocketmine-mp to 5.32.1 or later.

## Is CVE-2025-71417 being exploited?

There is no known exploitation of CVE-2025-71417 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71417 and fix it if it is affected.

What it is: CVE-2025-71417 is a high-severity denial of service vulnerability in pmmp PocketMine-MP, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-71417 in the wild and no public exploit code.

Affected packages and fixed versions:
- pocketmine/pocketmine-mp (Packagist): affected all versions; fixed in 5.32.1
- pocketmine/pocketmine-mp (Packagist): affected all versions; fixed in 5.32.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-71417/ (Markdown: https://insights.sbomify.com/CVE-2025-71417/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-71417
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-71417
- OSV: https://osv.dev/vulnerability/CVE-2025-71417

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-71417/
Summaries are generated and may contain mistakes; the official description above is the record.