Back

HIGH

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

Published Sep 15, 2026

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.

Affected products

Remediation

No remediation recorded yet.

References (6)

Change history (0)

No recorded changes yet.

Sources

CVE.org / MITRE

Status PUBLISHED
Assigner GitHub_M
Published Sep 15, 2026
Updated Sep 17, 2026
Reserved Jun 15, 2026

CISA Vulnrichment

Updated Sep 17, 2026

NVD

Status Received
Modified Sep 17, 2026

Red Hat

No data

ENISA EUVD

Assigner GitHub_M
Published Sep 15, 2026
Updated Sep 17, 2026