Unrated

Authentication Bypass in meta-ads-mcp

IdentifiersCVE-2026-54547CWE-306

CVE-2026-54547 is an authentication bypass vulnerability in meta-ads-mcp. In affected versions, the request authentication logic for the streamable HTTP MCP interface can incorrectly treat the presence of an X-Pipeboard-Token header as sufficient for access, allowing requests to be accepted without the required auth_token. When the server is configured with the operator's Meta access token, unauthenticated callers can cause MCP tool invocations to execute in the security context of that operator against the Meta Ads and Graph APIs.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated remote attacker to invoke MCP tool calls using the server operator's configured Meta access token. This can enable unauthorized reading and modification of Meta Ads resources available to that operator, including ad accounts, campaigns, creatives, audiences, insights, and budgets. It may also expose operator identity information returned by Meta Graph API operations. The vulnerability therefore results in unauthorized access and unauthorized actions against connected Meta Ads assets.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, do not expose meta-ads-mcp via the affected streamable HTTP mode while META_ACCESS_TOKEN is configured. Restrict network access to the MCP endpoint to trusted clients only, disable or avoid the vulnerable HTTP transport where possible, and remove the configured Meta access token from the runtime environment if the service is not required. X-Pipeboard-Token should not be treated as a standalone authentication credential.

Remediation

Patch, then assume compromise.

Upgrade meta-ads-mcp to version 1.0.115 or later. The corrective change is to enforce validation of the required auth_token for request acceptance and to prevent X-Pipeboard-Token from satisfying the authentication check on its own.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity