AWS Directs Multi Model Server Users to Migrate After Two Flaws
Tech GuruQuick Answer
AWS bulletin 2026-148-AWS covers CVE-2026-115812 and CVE-2026-115813 in every Multi Model Server release. Inventory MMS deployments, restrict interfaces and external URLs, migrate to a supported serving platform, validate models and integrations, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory MMS installations, exact builds, containers and forks, inference and management bindings, model archives and download sources, credentials, owners, and migration dependencies. Confirm actual Multi Model Server use and whether its unauthenticated management interface is network reachable. Do not infer exposure from SageMaker or another model-serving product alone. Discontinue MMS and migrate to a supported model-serving solution. For forks, implement AWS's archive-path and URL-allowlist corrections; until migration, bind the management interface to loopback when supported and restrict the serving port to trusted callers. Confirm the replacement platform, interface bindings and access controls, exercise trusted model loading and inference, review suspicious archives or outbound destinations where exposure existed, and retain migration evidence.
Last verified: 2026-10-24 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Amazon Web Services Multi Model Server (MMS) |
|---|---|
| Advisory | 2026-148-AWS |
| CVEs | CVE-2026-115812, CVE-2026-115813 |
| Authoritative release date | 2026-10-23 17:30:00 UTC |
| Authority revision date | 2026-10-23 17:30:00 UTC |
| Affected versions | Multi Model Server 1.1.11 and earlier, comprising every released version; network-accessible unauthenticated management interfaces increase risk. |
| Fixed version | No fixed release is available or planned because MMS is end of life; discontinue it and migrate to a supported model-serving solution |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | AWS does not state that these issues are being maliciously exploited.; no exploitation claim is inferred. |
What Changed
AWS disclosed path traversal during model archive extraction that can lead to code execution and a model-download SSRF path in the end-of-life Multi Model Server.
What To Validate Now
- Inventory. Inventory MMS installations, exact builds, containers and forks, inference and management bindings, model archives and download sources, credentials, owners, and migration dependencies.
- Establish applicability. Confirm actual Multi Model Server use and whether its unauthenticated management interface is network reachable. Do not infer exposure from SageMaker or another model-serving product alone.
- Remediate. Discontinue MMS and migrate to a supported model-serving solution. For forks, implement AWS's archive-path and URL-allowlist corrections; until migration, bind the management interface to loopback when supported and restrict the serving port to trusted callers.
- Validate. Confirm the replacement platform, interface bindings and access controls, exercise trusted model loading and inference, review suspicious archives or outbound destinations where exposure existed, and retain migration evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
MMS is end of life and has no fixed version. AWS says the loopback workaround is unavailable in some SageMaker-style configurations, so a generic configuration change must not be treated as complete remediation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
