PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-115812 – Path Traversal leading to RCE – AWS Multi Model Server ≤ 1.1.11

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-115812 is a relative path traversal vulnerability (CWE-23) in the model archive extraction of Amazon Web Services Multi Model Server (MMS) 1.1.11 and earlier. A crafted model archive might allow remote actors to execute arbitrary code. The CVSS v3.1 base score is 9.8 (Critical). MMS is end-of-life and no fixed version exists.

Technical details

  • Root cause: Relative path traversal during model archive extraction. Archive entries can be written outside the intended target directory.
  • Trigger conditions: MMS loads a crafted model archive. AWS notes that the MMS management interface does not require authentication, which compounds the issue.
  • Attack vector: Network. No privileges or user interaction are required.
  • Impact: Arbitrary file write beyond the extraction directory, which might lead to arbitrary code execution.
  • Related issue: The same AWS bulletin covers CVE-2026-115813, where the management interface could be misdirected to unintended network destinations. This is a separate CVE.

Affected software

  • AWS Multi Model Server: all released versions up to and including 1.1.11.
  • MMS reached end of life on November 20, 2025. Its repository is archived and read-only.

Severity

  • CVSS v3.1 base score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No patched version is available. AWS recommends discontinuing MMS and migrating to an actively supported model-serving alternative.
  • Derivative code: If you maintain derivative code, validate paths so that archive entries outside the extraction directory are rejected. Restrict model downloads to an approved URL allowlist.
  • If migration is not immediately feasible:
    • Bind the management interface to the loopback address only.
    • Do not accept externally supplied URLs for model downloads.
    • SageMaker deployments cannot apply the loopback workaround without disabling model loading. Prioritize migration for these deployments and restrict access to the serving port to trusted systems only.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge