CVE-2026-46555

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

July 20, 2026

Last Modified

August 18, 2026

Advisory Details (3)

Auto-updated Jul 20, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available

Unauthenticated bridge API allows message sending and arbitrary file exfiltration · Advisory · verygoodplugins/whatsapp-mcp · GitHub

https://github.com/verygoodplugins/whatsapp-mcp/security/advisories/GHSA-7jj9-4qqq-4xc4
github_release Patch Available

v0.2.1

Patch available: verygoodplugins/whatsapp-mcp v0.2.1

https://github.com/verygoodplugins/whatsapp-mcp/releases/tag/v0.2.1
generic🟡 PoC Available

whatsapp-mcp/SECURITY.md at main · verygoodplugins/whatsapp-mcp · GitHub

https://github.com/verygoodplugins/whatsapp-mcp/blob/main/SECURITY.md

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-11 09:23 UTCEG score recompute
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-09 11:52 UTCEG score recompute
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 22:52 UTCEG score recompute
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 21:06 UTCEG score recompute
  11. 2026-09-05 09:28 UTCEG score recompute
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-08-31 03:16 UTCEG score recompute
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 02:33 UTCEG score recompute
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 23:17 UTCEG score recompute
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 22:08 UTCEG score recompute
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 18:43 UTCEG score recompute
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 64 more
  1. 2026-08-24 19:21 UTCEG score recompute
  2. 2026-08-22 09:05 UTCEG score recompute
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 09:51 UTCEG score recompute
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 22:49 UTCEG score recompute
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-18 19:04 UTCEG score recompute▼ 0.60
  9. 2026-08-18 19:03 UTCNVD updateCVSS v3 → 7.1
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 17:33 UTCEG score recompute
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 18:11 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 06:34 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 07:20 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 08:05 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 21:11 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 21:54 UTCEG score recompute
  24. 2026-08-11 10:17 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-09 23:26 UTCEG score recompute
  27. 2026-08-09 13:46 UTCEPSS rescore
  28. 2026-08-08 00:57 UTCEG score recompute
  29. 2026-08-06 14:06 UTCEG score recompute
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-06 02:29 UTCEG score recompute
  32. 2026-08-05 19:17 UTCEPSS rescore
  33. 2026-08-05 00:36 UTCEG score recompute
  34. 2026-08-04 15:10 UTCEPSS rescore
  35. 2026-08-04 12:52 UTCEG score recompute
  36. 2026-08-04 10:39 UTCEPSS rescore
  37. 2026-08-03 11:55 UTCEG score recompute
  38. 2026-08-03 10:36 UTCEPSS rescore
  39. 2026-08-02 11:02 UTCEG score recompute
  40. 2026-08-02 02:27 UTCEPSS rescore
  41. 2026-08-01 11:48 UTCEG score recompute
  42. 2026-08-01 04:16 UTCEPSS rescore
  43. 2026-07-31 00:56 UTCEG score recompute
  44. 2026-07-30 16:28 UTCEPSS rescore
  45. 2026-07-30 13:18 UTCEG score recompute
  46. 2026-07-30 01:41 UTCEG score recompute
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-29 02:24 UTCEG score recompute
  49. 2026-07-28 15:36 UTCEPSS rescore
  50. 2026-07-27 15:23 UTCEG score recompute
  51. 2026-07-27 14:13 UTCEPSS rescore
  52. 2026-07-26 16:07 UTCEG score recompute
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-26 04:29 UTCEG score recompute
  56. 2026-07-25 14:18 UTCEPSS rescore
  57. 2026-07-24 14:17 UTCEPSS rescore
  58. 2026-07-23 14:18 UTCEPSS rescore
  59. 2026-07-23 03:17 UTCEG score recompute
  60. 2026-07-22 14:08 UTCEPSS rescore
  61. 2026-07-21 15:24 UTCEPSS rescore
  62. 2026-07-20 18:41 UTCEG score recompute
  63. 2026-07-20 17:10 UTCEG score recompute
  64. 2026-07-20 17:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-46555?
CVE-2026-46555 is a high vulnerability published on July 20, 2026. 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…
When was CVE-2026-46555 disclosed?
CVE-2026-46555 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46555 actively exploited?
CVE-2026-46555 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.4% of all scored CVEs.
What is the CVSS score of CVE-2026-46555?
CVE-2026-46555 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46555?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46555, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46555

Explore →

Is Your Infrastructure Affected by CVE-2026-46555?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs