CVE-2026-54547
Received Received - Intake

Auth Injection Bypass in Meta Ads MCP Server

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
CVE-2026-54547
EUVD
EUVD-2026-78886

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
meta meta_ads_mcp 1.0.115

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-287 When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Meta Ads MCP versions before 1.0.115. It allows unauthenticated access via HTTP streamable-http transport by sending any X-Pipeboard-Token value. The system incorrectly accepts this as valid, bypassing proper authentication checks and using the server operator's META_ACCESS_TOKEN instead. This grants access to the operator's Meta Ads data.

Detection Guidance

Check the Meta Ads MCP server version. If it is below 1.0.115, the system is vulnerable. Inspect HTTP headers for requests using X-Pipeboard-Token without proper authentication. Monitor for unauthorized access to Meta Ads data or unexpected use of META_ACCESS_TOKEN.

Impact Analysis

An attacker could exploit this to read or modify your Meta Ads data without proper authorization. This could lead to unauthorized changes to ad campaigns, data leaks, or misuse of your advertising account. Only deployments using streamable-http transport with META_ACCESS_TOKEN set are affected.

Mitigation Strategies

Upgrade Meta Ads MCP to version 1.0.115 or later. Ensure HTTP requests require both auth_token and pipeboard_token for authentication. Disable X-Pipeboard-Token as a fallback credential. Review server logs for suspicious activity related to Meta Ads data access.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54547. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart