Skip to content

← Actionable
Medium, CVSS 5.3

pocketmine/raklib reliable-ordered queue size is unlimited, allowing a session to hog server memory

GHSA-w98g-5fmx-wm4x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pocketmine/raklib 0.15.1, 0.14.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Packagist pocketmine/raklib

    Affected
    >= 0.14.0, < 0.14.6>= 0.15.0, < 0.15.1
    Fixed in
    0.15.1, 0.14.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact A client can send reliable-ordered packets 0, 2, 3, 4, 5 ... etc, and all the packets 2 and up will stay in the reliable-ordered queue until 1 arrives. A malicious client can exploit this to waste all available server memory by simply never sending the missing packet. Since the server doesn't make any effort to limit the size of the queue or detect this kind of abuse, this problem is easy to abuse. Patches This bug was fixed on the 0.14.x and 0.15.x release lines by 371190f5854372154d1b263cd2a10e658e92bebe. Workarounds No workaround is known.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-w98g-5fmx-wm4x

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-w98g-5fmx-wm4x

Advisory: pocketmine/raklib reliable-ordered queue size is unlimited, allowing a session to hog server memory
IDs: GHSA-w98g-5fmx-wm4x
Record: https://patchnext.com/advisories/ghsa-w98g-5fmx-wm4x (revision 1, source checked 26 Oct 2026, 14:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pocketmine/raklib 0.15.1, 0.14.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pocketmine/raklib: affected >= 0.14.0, < 0.14.6; >= 0.15.0, < 0.15.1; fixed in 0.15.1, 0.14.6

## Suggested inspection (read-only)
- Packagist pocketmine/raklib: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pocketmine/raklib.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w98g-5fmx-wm4x (GitHub-reviewed advisory GHSA-w98g-5fmx-wm4x lists affected ranges: Packagist pocketmine/raklib >=0.14.0 =0.15.0 <0.15.1)

Commands are suggestions: review each one before running it.

Loading voting…