Meta Ads MCP: X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token (CVE-2026-54547) | HOL Guard CVE

High severityCVE-2026-54547GHSA-2V2F-MVFG-PH56

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

Answer in brief

CVE-2026-54547 records a High severity vulnerability in Meta Ads MCP: X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token. The current sources do not mark it as known exploited. The current feed maps pipeboard-co/meta-ads-mcp (generic), meta-ads-mcp (pip). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 15, 2026Updated Sep 15, 2026Source checked Sep 17, 2026First seen by HOL Jul 17, 2026Material review Sep 15, 2026

Upstream Advisory

Key facts

Risk: High
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps pipeboard-co/meta-ads-mcp (generic), meta-ads-mcp (pip). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
pipeboard-co/meta-ads-mcpgeneric	< 1.0.115	Not reported
meta-ads-mcppip	<1.0.115	1.0.115

Recommended response

Check inventory. Check lockfiles and deployed manifests for pipeboard-co/meta-ads-mcp, meta-ads-mcp.
Review the reported fix. Update meta-ads-mcp to 1.0.115 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.