CVE-2026-46555

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (10th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-46037 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 20, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Jul 20, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

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
Web page

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 8× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 146 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 46 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46555?
CVE-2026-46555 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-46555 published?
The CVE record for CVE-2026-46555 was published on July 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-46555 actively exploited?
CVE-2026-46555 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-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?
A fix for CVE-2026-46555 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs