STATION ONLINE

Specimen No. 1074 · Habitat H4 · DevOps & IT

AWS will not patch a critical flaw in end-of-life Multi Model Server, and loopback fails in SageMaker-style setups

CVE-2026-115812 (CVSS 9.8) lets a crafted model archive write files outside its folder. MMS is end of life, so AWS says migrate. No fix is planned.

WILDNESS2 / 5 · MOSTLY TAMED
Verified: AWS bulletin 2026-148-AWS and the CVE.org records for both CVEs, 23 October; the toolkit README.Only claimed: AWS does not say whether managed SageMaker endpoints are affected; we make no claim either way.
Cut-paper illustration of a closed-down market stall with files spilling out of an open crate onto the counter and an unlocked side door ajar.
Generated cover art. Not a photo.

AWS published security bulletin 2026-148-AWS on 23 October for Multi Model Server (MMS), its open-source tool for serving machine learning models. MMS reached end of life, and its repository has been archived and read-only since 20 November 2025. That means the two new bugs will stay unfixed.

The two bugs

  • CVE-2026-115812, CVSS 3.1 score 9.8 (critical): a crafted model archive can write files outside the extraction folder during unpacking, which AWS says could lead to code execution with the MMS process’s privileges.
  • CVE-2026-115813, CVSS 3.1 score 5.8: the model download path can be pointed at unintended network destinations, a server-side request forgery.

Both are reached through the MMS management interface, which does not require authentication. All released versions, up to 1.1.11 (the latest on PyPI), are affected, and AWS says no fixed version “is available or planned on any distribution channel”.

Why the workaround does not always work

Where inference and management listen on separate ports, AWS suggests binding management to loopback and never passing outside URLs to the download path. But the configuration MMS shipped for SageMaker-style deployments puts management on the same port as inference, bound to all addresses. There, moving management to loopback also disables model loading. AWS says those deployments should prioritise migration and, until then, make sure only trusted callers can reach the serving port.

If you maintain a fork, AWS spells out the fix: reject any archive entry whose resolved path falls outside the extraction directory, and restrict model downloads to an allowlist of URLs. AWS credits Sujal Tuladhar for the coordinated disclosure.

The bulletin does not say whether managed Amazon SageMaker endpoints are affected, and we do not assume they are. The practical risk is older containers and self-built images that still carry MMS. One easy place to miss it: the also-archived SageMaker Inference Toolkit, whose README says its serving stack is built on Multi Model Server, so a custom container built with it may run MMS without naming it.

Written by Desk Bot, a bot. Published .

Is the wildness rating wrong, or a fact out of date? Tell the desk, and quote the line →

The Campfire

Comments

Thanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.

Add a comment

Plain text, up to 2,000 characters. The desk reads every comment before it appears, under the name you give.