Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta Ads. Prior to version 1.0.115, AuthInjectionMiddleware in meta_ads_mcp/core/http_auth_integration.py rejects HTTP MCP requests only when both auth_token and pipeboard_token are absent, while extract_token_from_headers() does not recognize X-Pipeboard-Token as a primary credential. A network caller using the streamable-http transport can therefore send any X-Pipeboard-Token value, pass the guard without establishing authentication context, and cause get_auth_token() to fall back to the server operator's META_ACCESS_TOKEN. Subsequent MCP tools execute with the operator's Meta credentials and can read or modify the operator's Meta Ads data. Deployments using the default stdio transport or without META_ACCESS_TOKEN are not affected. This issue is fixed in version 1.0.115.
CVE-2026-54547
This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(medium)
- EG Risk
- 49(Track*)EG Risk 49/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 computedSeverity74% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
September 17, 2026
Advisory Details (4)
Auto-updated Sep 15, 20261.0.115
Patch available: pipeboard-co/meta-ads-mcp 1.0.115
https://github.com/pipeboard-co/meta-ads-mcp/releases/tag/1.0.115commit 95e852793b7f (pipeboard-co/meta-ads-mcp)
Patch available: pipeboard-co/meta-ads-mcp 1.0.115 (contains commit 95e852793b7f)
https://github.com/pipeboard-co/meta-ads-mcp/commit/95e852793b7ff8604a8132e85d5facd08c91a36efix(auth): require a primary access-token credential at the HTTP middleware (1.0.114)
Patch available: pipeboard-co/meta-ads-mcp 1.0.115 (PR #137 merged 2026-06-05)
https://github.com/pipeboard-co/meta-ads-mcp/pull/137X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token · Advisory · pipeboard-co/meta-ads-mcp · GitHub
https://github.com/pipeboard-co/meta-ads-mcp/security/advisories/GHSA-2v2f-mvfg-ph56Vendor Advisories for CVE-2026-54547(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| meta-ads-mcp | 0.1.0 ... 1.0.99 (172 versions) | 1.0.115 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× 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.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 07:27 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 18:15 UTCEG score recompute
- 2026-09-17 10:15 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 18:36 UTCEG score recompute
- 2026-07-30 09:29 UTCEG score recompute
- 2026-07-26 11:18 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-17 19:00 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(5)
What is CVE-2026-54547?
When was CVE-2026-54547 disclosed?
Is CVE-2026-54547 actively exploited?
What is the CVSS score of CVE-2026-54547?
How do I remediate CVE-2026-54547?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54547
Is Your Infrastructure Affected by CVE-2026-54547?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.