PatchSiren cyber security CVE debrief
CVE-2026-46555 verygoodplugins CVE debrief
The WhatsApp MCP Server, enabling Claude to read and send WhatsApp messages, has vulnerabilities allowing unauthorized message sending and file reading due to lack of authentication and Host header validation. Users should be aware of these issues and address them to prevent unauthorized access and data exfiltration. The CVE record was published on 2026-07-20T17:17:09.820Z and has not been modified since then. The NVD entry is currently Analyzed. Affected product deployments should be identified in managed environments, and owners should be assigned for follow-up. Official advisories or CVE records should be reviewed to validate affected scope, severity, and vendor guidance. Vendor-supported updates or mitigations should be planned through normal change control where exposure is confirmed. Compensating controls should be reviewed for exposed systems while remediation is scheduled and verified. Relevant monitoring, detection, and logs should be checked for exposed assets that need extra review.
- Vendor
- verygoodplugins
- Product
- whatsapp-mcp
- CVSS
- HIGH 7.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-20
- Original CVE updated
- 2026-08-18
- Advisory published
- 2026-07-20
- Advisory updated
- 2026-08-18
Who should care
Users of WhatsApp MCP Server, especially those running versions prior to 0.2.1, should be aware of and address these vulnerabilities to prevent unauthorized access and data exfiltration. Affected operators, platforms, vulnerability-management, and security teams should prioritize upgrading to version 0.2.1 or later. They should also review compensating controls for exposed systems while remediation is scheduled and verified. Relevant monitoring, detection, and logs should be checked for exposed assets that need extra review. Exceptions should be tracked, and remediated assets should be retested and closed only after evidence is documented. Asset inventory and source tracking should be updated accordingly. Rolling back change windows and verifying source tracking are also recommended. Confirmed exposure should be addressed through normal change control. Managed environments should identify affected product deployments and assign owners for follow-up. Official advisories or CVE records should be reviewed to validate affected scope, severity, and vendor guidance. Compensating controls should be implemented where possible. Monitoring and detection capabilities should be reviewed to ensure adequate coverage. Security teams should verify that all necessary steps are taken to mitigate the vulnerabilities. Vulnerability management processes should be updated to include checks for WhatsApp MCP Server vulnerabilities. Asset owners should be notified and involved in the remediation process. Security teams should also review the configuration of the WhatsApp MCP Server to ensure that it is properly secured. The security team should track the status of remediation efforts and verify that all affected systems are patched or mitigated. They should also review the incident response plan to ensure that it includes procedures for responding to WhatsApp MCP Server vulnerabilities. Security teams should communicate with stakeholders to ensure that they are aware of the vulnerabilities and the necessary steps to mitigate them. They should also review the WhatsApp MCP Server documentation to ensure that it is up-to-date and accurate. The security team should verify that all necessary
Technical summary
The WhatsApp MCP Server has vulnerabilities allowing unauthorized message sending and file reading due to lack of authentication and Host header validation. Version 0.2.1 fixes these issues by introducing bearer token authentication on the bridge HTTP API, host header allow-list validation to prevent DNS rebinding, and confinement of `media_path` to a configured directory. Users should upgrade to version 0.2.1 or later to address authentication and path traversal vulnerabilities. The WhatsApp MCP Server enables Claude to read and send WhatsApp messages. Prior to version 0.2.1, the `whatsapp-bridge` HTTP API listens on `127.0.0.1:8080` without authentication and without Host header validation, and the `/api/send` endpoint accepts an absolute `media_path` parameter without confining it to a safe directory.
Defensive priority
WhatsApp MCP Server users should prioritize upgrading to version 0.2.1 or later to address authentication and path traversal vulnerabilities.
Recommended defensive actions
- Upgrade WhatsApp MCP Server to version 0.2.1 or later
- Implement bearer token authentication for the bridge HTTP API
- Restrict access to port 8080 when not in use
- Avoid running the bridge with untrusted MCP servers or processes
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
Evidence notes
The WhatsApp MCP Server vulnerability allows unauthorized sending of WhatsApp messages, reading of arbitrary files, and potential exfiltration of sensitive data. Users should upgrade to version 0.2.1 for fixes.
Official resources
-
CVE-2026-46555 CVE record
CVE.org
-
CVE-2026-46555 NVD detail
NVD
-
Source item URL
nvd_modified
-
Source reference
[email protected] - Issue Tracking
-
Mitigation or vendor reference
[email protected] - Product, Release Notes
-
Mitigation or vendor reference
[email protected] - Mitigation, Patch, Vendor Advisory
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-20T17:17:09.820Z and has not been modified since then.