CVE-2026-54547: pipeboard-co meta-ads-mcp · Improper Authentication
Affects pipeboard-co meta-ads-mcpSource CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 1.0.115 soon.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.115
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade meta-ads-mcp and pipeboard-co/meta-ads-mcp to 1.0.115.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pipeboard-cometa-ads-mcp | Affected
| Fixed in
|
GitHubpipeboard-co/meta-ads-mcppkg:github/pipeboard-co/meta-ads-mcpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade meta-ads-mcp to version 1.0.115 or later, where this authentication issue is fixed. If upgrading is not immediately possible, avoid using the streamable-http transport or remove the META_ACCESS_TOKEN environment variable to prevent fallback authentication. No other mitigations are specified.
Description
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.
References
- github.com/pipeboard-co/meta-ads-mcp/security/advisories/GHSA-2v2f-mvfg-ph56 (opens in a new tab)
- github.com/pipeboard-co/meta-ads-mcp/pull/137 (opens in a new tab)
- github.com/pipeboard-co/meta-ads-mcp/commit/95e852793b7ff8604a8132e85d5facd08c91a36e (opens in a new tab)
- github.com/pipeboard-co/meta-ads-mcp/releases/tag/1.0.115 (opens in a new tab)