Files
vuln-cve/data/2026/46xxx/CVE-2026-46555.json
T

152 lines
7.8 KiB
JSON

{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-46555",
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"state": "PUBLISHED",
"assignerShortName": "GitHub_M",
"dateReserved": "2026-05-14T20:42:31.369Z",
"datePublished": "2026-07-20T17:06:22.232Z",
"dateUpdated": "2026-07-20T17:35:17.593Z"
},
"containers": {
"cna": {
"title": "WhatsApp MCP: Unauthenticated bridge API allows message sending and arbitrary file exfiltration",
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-22",
"lang": "en",
"description": "CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-306",
"lang": "en",
"description": "CWE-306: Missing Authentication for Critical Function",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-346",
"lang": "en",
"description": "CWE-346: Origin Validation Error",
"type": "CWE"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 7.7,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
}
}
],
"references": [
{
"name": "https://github.com/verygoodplugins/whatsapp-mcp/security/advisories/GHSA-7jj9-4qqq-4xc4",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/verygoodplugins/whatsapp-mcp/security/advisories/GHSA-7jj9-4qqq-4xc4"
},
{
"name": "https://github.com/verygoodplugins/whatsapp-mcp/blob/main/SECURITY.md",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/verygoodplugins/whatsapp-mcp/blob/main/SECURITY.md"
},
{
"name": "https://github.com/verygoodplugins/whatsapp-mcp/releases/tag/v0.2.1",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/verygoodplugins/whatsapp-mcp/releases/tag/v0.2.1"
}
],
"affected": [
{
"vendor": "verygoodplugins",
"product": "whatsapp-mcp",
"versions": [
{
"version": "< 0.2.1",
"status": "affected"
}
]
}
],
"providerMetadata": {
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M",
"dateUpdated": "2026-07-20T17:06:22.232Z"
},
"descriptions": [
{
"lang": "en",
"value": "WhatsApp MCP Server is a Model Context Protocol (MCP) server for WhatsApp, enabling 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. Combined, these issues allow any local process running as the same user as the bridge to send WhatsApp messages from the paired account without authorization; the same caller to read arbitrary files readable by the user (e.g. SSH private keys, browser session data, source code, dotfiles) and exfiltrate them as WhatsApp document attachments; and/or a remote attacker to trigger the same operations via DNS rebinding from a webpage the user visits, since no Host header validation is performed. In MCP environments, \"local caller\" extends beyond processes the user explicitly launched — sibling MCP servers, IDE extensions, and tool-triggered flows running in the user's session can act as the effective caller. This issue is fixed in whatsapp-mcp v0.2.1 and corresponding Docker images / release artifacts. Users should upgrade immediately. The fix introduces bearer token authentication on the bridge HTTP API (configured via environment variable, required on all requests, validated with constant-time comparison); host header allow-list validation to prevent DNS rebinding; and confinement of `media_path` to a configured directory, with rejection of absolute paths outside the root and path traversal sequences. This is a breaking change for clients of the bridge API. For users who cannot immediately upgrade: Stop the bridge, or block loopback access to port 8080, when the bridge is not actively in use; avoid running the bridge alongside untrusted MCP servers, browser extensions, or other untrusted local processes; avoid browsing untrusted sites while the bridge is running (DNS rebinding mitigation); and/or run the bridge under a dedicated user account or in a sandbox/container with no access to sensitive files."
}
],
"source": {
"advisory": "GHSA-7jj9-4qqq-4xc4",
"discovery": "UNKNOWN"
}
},
"adp": [
{
"metrics": [
{
"other": {
"type": "ssvc",
"content": {
"timestamp": "2026-07-20T17:35:08.494886Z",
"id": "CVE-2026-46555",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"version": "2.0.3"
}
}
}
],
"title": "CISA ADP Vulnrichment",
"providerMetadata": {
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP",
"dateUpdated": "2026-07-20T17:35:17.593Z"
}
}
]
}
}