CVE-2026-54547: pipeboard-co meta-ads-mcp auth bypass via X-Pipeboard-Token header

CVE-2026-54547 · Severity: high · CVSS 7.4 · Published 2026-09-15

A vulnerability in the meta-ads-mcp library allows unauthorized users to bypass security checks and access sensitive Meta Ads data. By sending a specific header in a web request, an attacker can trick the system into using the server administrator's own credentials. This allows the attacker to read or modify advertising campaigns, budgets, and account details as if they were the administrator.

Technologies: meta-ads-mcp (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-54547 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54547 being exploited in the wild.
How severe is CVE-2026-54547?
High severity, with a CVSS score of 7.4, published 15 September 2026.
Which products and versions are affected?
meta-ads-mcp (PyPI) < 1.0.115, ECOSYSTEM:introduced=0,fixed=1.0.115.
Is there a fix for CVE-2026-54547?
Yes. meta-ads-mcp (PyPI): upgrade to 1.0.115 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54547 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-54547?
Check whether you run meta-ads-mcp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • meta-ads-mcp (PyPI): upgrade to 1.0.115 or later
    pip install "meta-ads-mcp>=1.0.115"

Technical details

The AuthInjectionMiddleware in meta-ads-mcp contains a logic flaw in its authentication guard condition. The middleware only rejects requests if both auth_token and pipeboard_token are absent. However, the extract_token_from_headers() function does not recognize the 'X-Pipeboard-Token' header, while extract_pipeboard_token_from_headers() does. By providing only the 'X-Pipeboard-Token' header, an attacker causes auth_token to be None while pipeboard_token is truthy, bypassing the 401 Unauthorized response. Because no valid user context is established, the system falls back to the META_ACCESS_TOKEN environment variable, allowing the attacker to perform privileged Meta Graph API operations. This affects deployments using the 'streamable-http' transport mode.

Affected products

  • pipeboard-co meta-ads-mcp < 1.0.115

Identifiers

  • CVE-2026-54547
  • GHSA-2v2f-mvfg-ph56
  • PYSEC-2026-3484

Timeline

  • 2026-06-05: advisory: GitHub Advisory published
  • 2026-07-17: disclosed: Vulnerability disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.