Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-63252: In Eclipse Milo versions 0.6.0 through 1.1.4, UASC server transport handlers fail to release retained partial

43
This month
HIGH 7.5REMOTEUPGRADE

CVE-2026-63252 is a high-severity flaw (CVSS 7.5) affecting milo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Eclipse Milo versions 0.6.0 through 1.1.4, UASC server transport handlers fail to release retained partial message chunks when a channel disconnects, allowing a remote unauthenticated client to exhaust pooled direct memory by repeatedly sending incomplete chunks and disconnecting, potentially terminating the server.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 53%)
CISA exploited listNo
WeaknessCWE-401
Published2026-08-04
Last modified2026-10-23
Publisher (CNA): Eclipse Foundation · Vendor: eclipse

Last updated 2026-10-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

eclipse milo UPGRADE
Affected: >= 0.6.0 and < 1.1.5
Fixed in: 1.1.5
Safe to downgrade to: a release before 0.6.0
1. Check installed version
apt-cache policy milo || rpm -q milo || milo --version
2. UPGRADE to 1.1.5 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade milo
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade milo
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.6.0 (Debian / Ubuntu)
apt-cache madison milo sudo apt install milo=<VERSION_BEFORE_0.6.0> sudo apt-mark hold milo
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list milo sudo dnf downgrade milo-<VERSION_BEFORE_0.6.0> sudo dnf versionlock add milo
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Fedora 46 · kwin-zones · FIXED · 1.0.13-1.fc46 · FEDORA-2026-95888f332b · source
sudo dnf upgrade --advisory=FEDORA-2026-95888f332b
Fedora ELN · nginx-mod-brotli · FIXED · 1.0.0~rc-16.eln159 · FEDORA-2026-501a6a8273 · source
sudo dnf upgrade --advisory=FEDORA-2026-501a6a8273
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-63252?

milo: upgrade to 1.1.5. Exact commands for each OS are on this page.

Is CVE-2026-63252 being exploited?

CVE-2026-63252 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-63252 affect?

CVE-2026-63252 affects milo. Severity is high (CVSS 7.5). In Eclipse Milo versions 0.6.0 through 1.1.4, UASC server transport handlers fail to release retained partial message chunks when a channel disconnects, allowing a remote unauthenticated client to exhaust pooled direct memory by repeatedly

How urgent is CVE-2026-63252?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs