# CVE-2026-7461: OS Command Injection in Amazon ECS Agent via FSx Windows File Server Volume Credentials

> Remote authenticated attackers can execute shell commands with SYSTEM privileges on Windows hosts via crafted ECS task definitions.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Apr 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-fc67-c4hg-q653, GHSA-w2r9-8jfw-7fpr, GO-2026-5353

## What is CVE-2026-7461?

CVE-2026-7461 is a high-severity command injection vulnerability in AWS Amazon ECS Agent, published on 30 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper neutralization of inputs used in an OS command in the FSx Windows File Server volume mounting component in Amazon ECS Agent on Windows before version 1.103.0 might allow a remote authenticated threat actor to execute shell commands with SYSTEM privileges on the underlying host via a specially crafted username field in an ECS task definition. This issue requires permissions to register ECS task definitions or write to the Secrets Manager or SSM Parameter Store credentials used by the FSx volume configuration.

To remediate this issue, users should upgrade to version 1.103.0.

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

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

3 open source packages ship an affected version, including github.com/aws/amazon-ecs-agent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/aws/amazon-ecs-agent` | Go | From 1.47.0 | 1.103.0 |
| `github.com/aws/amazon-ecs-agent` | Go | From 1.47.0 | 1.103.0 |
| `github.com/aws/amazon-ecs-agent` | Go | From 1.47.0 | 1.103.0 |

Products: Amazon Amazon Ecs Container Agent.

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

Upgrade github.com/aws/amazon-ecs-agent to 1.103.0 or later.

## Is CVE-2026-7461 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7461 is a high-severity command injection vulnerability in AWS Amazon ECS Agent, published on 30 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7461 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/aws/amazon-ecs-agent (Go): affected from 1.47.0; fixed in 1.103.0
- github.com/aws/amazon-ecs-agent (Go): affected from 1.47.0; fixed in 1.103.0
- github.com/aws/amazon-ecs-agent (Go): affected from 1.47.0; fixed in 1.103.0

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-7461/ (Markdown: https://insights.sbomify.com/CVE-2026-7461/index.md)
```

## Sources

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

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