# CVE-2026-115813: Server-side request forgery in the model download path in Amazon Web Services Multi Model Server


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-g55x-6xv3-fpjr

## What is CVE-2026-115813?

CVE-2026-115813 is a medium-severity vulnerability in AWS multi-model-server, published on 23 Oct 2026. 

### Official description

Server-side request forgery in the model download path in Amazon Web Services Multi Model Server 1.1.11 and earlier might allow remote actors to send requests to internal network destinations via a crafted model URL.

Multi Model Server is end of life and no fixed version is available. Users should discontinue use of Multi Model Server and migrate to a supported model serving solution.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-115813?


## How do I fix CVE-2026-115813?

No fix has been published for CVE-2026-115813 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115813 being exploited?

There is no known exploitation of CVE-2026-115813 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115813 and fix it if it is affected.

What it is: CVE-2026-115813 is a medium-severity vulnerability in AWS multi-model-server, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115813 in the wild and no public exploit code.

Affected product: AWS multi-model-server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115813/ (Markdown: https://insights.sbomify.com/CVE-2026-115813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115813
- OSV: https://osv.dev/vulnerability/CVE-2026-115813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115813/
Summaries are generated and may contain mistakes; the official description above is the record.