# CVE-2025-5277: Command injection in aws-mcp-server

> An attacker can execute arbitrary commands on the host system by crafting a malicious prompt accessed by the MCP client.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 May 2025
- **Updated:** 28 May 2025

## What is CVE-2025-5277?

CVE-2025-5277 is a critical command injection vulnerability in alexei-led aws-mcp-server, published on 28 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

aws-mcp-server MCP server is vulnerable to command injection. An attacker can craft a prompt that once accessed by the MCP client will run arbitrary commands on the host system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-5277 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5277 is a critical command injection vulnerability in alexei-led aws-mcp-server, published on 28 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-5277 in the wild and no public exploit code.

Affected product: alexei-led aws-mcp-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-2025-5277/ (Markdown: https://insights.sbomify.com/CVE-2025-5277/index.md)
```

## Sources

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

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