CVE-2026-54547 Meta Ads MCP: X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token
Attackers can bypass authentication by sending an X-Pipeboard-Token header, causing the server to execute actions using the operator's Meta credentials.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54547?
CVE-2026-54547 is a high-severity authentication bypass vulnerability in pipeboard-co meta-ads-mcp, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-287
Which versions are affected by CVE-2026-54547?
3 open source packages ship an affected version, including meta-ads-mcp.
| Package | Affected | Fixed in |
|---|---|---|
meta-ads-mcp PyPI | All versions | 1.0.115 |
meta-ads-mcp PyPI | All versions | 1.0.115 |
meta-ads-mcp PyPI | All versions | 1.0.115 |
How do I fix CVE-2026-54547?
Upgrade meta-ads-mcp to 1.0.115 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-54547 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54547 exists.
Sources
Also known as GHSA-2v2f-mvfg-ph56, PYSEC-2026-3484.