Key points
- The flaw affects aws-healthomics-mcp-server versions 0.0.35 and earlier.
- AWS version 0.0.36 resolves the path traversal and arbitrary file write issue.
- Attackers must be able to influence the MCP agent to exploit this vulnerability.
AWS HealthOmics users running the MCP Server must update immediately. The vendor released version 0.0.36 to fix a security gap in earlier builds. This patch addresses a path traversal flaw that could let threat actors write files outside designated directories. The issue impacts any installation using version 0.0.35 or older.
In plain English
The vulnerability exists in the workflow linting tools of the server. The software failed to properly restrict file paths to a safe folder. An attacker who can control the MCP agent input could use directory traversal sequences. This allows them to place malicious files in arbitrary locations on the host system. The intended workflow bundle directory is no longer the only target.
The background
AWS HealthOmics is a service that manages infrastructure for bioinformatics analyses. It supports clinical diagnostics, drug discovery, and agricultural research at scale. The service is HIPAA-eligible, handling sensitive data. The specific component affected is the aws-healthomics-mcp-server. The flaw was identified through a coordinated disclosure process. Rotimi Akinyele from Deriv reported the issue to AWS.
What changes now
Users must upgrade to version 0.0.36 to resolve the issue. AWS states that this version incorporates the necessary fixes. Anyone using forked or derivative code must also patch their installations. The vendor recommends ensuring all instances are updated to the latest version. No other mitigation steps are listed in the advisory.
Who needs to act first
Teams should prioritize systems exposed to untrusted inputs or external agents. Check whether your deployment allows outside influence on the MCP agent. Roll out the update to the most exposed environments first. Test the new version in a non-production setting before a full rollout. Back up your current configurations and data before making changes. Monitor logs for unusual file creation activities during the transition period.
What to do and how to stay safe: AWS
- Verify your current aws-healthomics-mcp-server version and compare it to 0.0.36.
- Upgrade to the patched version as soon as maintenance windows allow.
- Review access controls for the MCP agent to limit potential influence.
- Monitor file system integrity for unexpected changes in write permissions.
Step-by-step guide: Out-of-Band Patches: Meaning, Risks, and Deployment Reality
General security guidance from the Patch Herald newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Which versions of the server are vulnerable?
All versions of aws-healthomics-mcp-server up to and including 0.0.35 are affected by this flaw.
Is there a fix available for this vulnerability?
Yes, AWS has released version 0.0.36 which addresses the path traversal and file write issue.
Who reported this security issue to AWS?
Rotimi Akinyele from Deriv collaborated with AWS through the coordinated vulnerability disclosure process.
