# CVE-2025-65200: An issue was discovered in localstack 4.9.2 allowing attackers to execute arbitrary code via crafted content hosted on a web-accessable URL


- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-xgg2-59hm-7r89

## What is CVE-2025-65200?

CVE-2025-65200 is a critical vulnerability in n/a, published on 22 Oct 2026. 

### Official description

An issue was discovered in localstack 4.9.2 allowing attackers to execute arbitrary code via crafted content hosted on a web-accessable URL and when passed said URL in the the templateURL to the _localstack/cloudformation/deploy endpoint, the hosted content can get executed in the context of the docker container.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-65200?


## How do I fix CVE-2025-65200?

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

## Is CVE-2025-65200 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65200 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65200 and fix it if it is affected.

What it is: CVE-2025-65200 is a critical vulnerability in n/a, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65200 exists.

Affected product: n/a. 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-2025-65200/ (Markdown: https://insights.sbomify.com/CVE-2025-65200/index.md)
```

## Sources

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

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