aerostack-mcp WhatsApp Media URL SSRF Vulnerability
A security vulnerability has been detected in aerostackdev aerostack-mcp up to 6315dfde7df0a15aaf743f88d91347115e09ba23. Affected by this issue is the function upload_media of the component mcp-whatsapp. Such manipulation of the argument media_url leads to server-side request forgery. The attack may be launched remotely. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.
Quick answer
aerostackdev aerostack-mcp should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Rolling release up to 6315dfde7df0a15aaf743f88d91347115e09ba23
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
aerostack-mcp is affected by a server-side request forgery issue in the mcp-whatsapp upload_media function through the media_url argument. Because NVD indicates a rolling release and no fixed version details, avoid exposing the affected function until a trusted patch or upstream commit is available. Treat deployments with internal network access as higher risk.
- Inventory aerostack-mcp deployments and determine whether the mcp-whatsapp upload_media function is reachable.
- Update to the latest trusted upstream commit or vendor-supported patched release when available.
- Disable or restrict upload_media and external media_url handling until a fix is verified.
- Block access from the service to cloud metadata endpoints, loopback addresses, private networks, and internal admin services.
- Validate media_url inputs with allow-listed schemes, hosts, redirects, and content types before server-side fetches.
- Review outbound HTTP logs for requests to internal IP ranges, metadata services, or unexpected domains.
- Rotate tokens and credentials reachable from the host if SSRF access to internal resources is suspected.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the deployed aerostack-mcp commit includes a verified fix or that upload_media is disabled.
- Validate media_url cannot fetch loopback, private, link-local, metadata, or internal service addresses.
- Review application and egress logs for SSRF attempts during the vulnerable window.
- Test legitimate media upload workflows with approved external URLs only.
- Run a Fixnx scan and confirm no public MCP administration or unsafe upload endpoint is exposed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-15189?
aerostackdev aerostack-mcp versions listed as affected should be reviewed: Rolling release up to 6315dfde7df0a15aaf743f88d91347115e09ba23.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
Why can this risk appear in multiple categories?
A vulnerability can belong to more than one platform or ecosystem. Fixnx keeps one canonical risk page while also listing it in every relevant category.