AWS Fixes Diff-Scan Argument Injection in security-agent-mcp-server
Tech GuruQuick Answer
AWS bulletin 2026-121 covers security-agent-mcp-server versions 0.1.1 through versions before 0.2.0. A crafted Git reference can be interpreted as a command option, allowing files outside the repository workspace to be created, overwritten or truncated. Upgrade the server actually launched by your MCP client to 0.2.0 or later; AWS lists no workaround other than upgrading.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory AWS security-agent-mcp-server 0.1.1 through 0.1.x, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-10-01 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | AWS security-agent-mcp-server 0.1.1 through 0.1.x |
|---|---|
| Advisory | 2026-121-AWS |
| CVE | CVE-2026-97662 |
| Authoritative release date | 2026-10-01 17:30:00 UTC |
| Authority revision date | 2026-10-01 17:30:00 UTC |
| Affected versions | security-agent-mcp-server releases 0.1.1 and later but before 0.2.0 when untrusted reference values reach the diff-scan operation. |
| Fixed version | security-agent-mcp-server 0.2.0 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The fix concerns how the server passes repository references to a Git command. Restricting work to trusted repositories and using a least-privileged isolated environment can reduce exposure while arranging the upgrade, but neither replaces it. Check forks and derived packages for incorporation of the fix.
What To Validate Now
- Inventory. Locate AWS security-agent-mcp-server 0.1.1 through 0.1.x deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: security-agent-mcp-server releases 0.1.1 and later but before 0.2.0 when untrusted reference values reach the diff-scan operation. Do not infer applicability from product family or severity alone.
- Remediate. Upgrade to 0.2.0. Until then, scan only trusted repositories and run the server as a least-privileged user in an isolated environment; AWS states there is no other workaround.
- Validate. Inspect the MCP client configuration and the version in its launched server environment, not just a similarly named global installation. Reconnect or restart that server through normal management, then perform an ordinary diff in an authorized disposable repository. Review unexpected file changes without running an exploit or treating a successful diff as proof of no prior damage.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
