CVE-2026-54547

published 15 Sep 2026 · updated 17 Sep 2026

Meta Ads MCP: X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token

7.4HighCVSS 7.4EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
pipeboard-co<1.0.115

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-54547 severity on Zeptric[![CVE-2026-54547](https://zeptric.io/badge/cve/CVE-2026-54547.svg)](https://zeptric.io/cve/CVE-2026-54547)