meta-ads-mcp: X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-54547: 0.52% estimated exploitation activity in the next 30 days; percentile 44.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token Summary AuthInjectionMiddleware in meta-ads-mcp rejects HTTP MCP requests only when both authtoken and pipeboardtoken are absent. Because extracttokenfromheaders() does not recognise the X-Pipeboard-Token header, an attacker who sends that header with any arbitrary value produces authtoken = None and pipeboardtoken = <attacker value, making the guard condition evaluate to False and passing the request through. No authentication context is set; the token getter falls back to the server operator's METAACCESSTOKEN environment variable. Every subsequent MCP tool call executes with the operator's Meta credentials, allowing an unauthenticated network caller to read and write the operator's Meta Ads data. Details The vulnerable condition is at metaadsmcp/core/httpauthintegration.py:259: extracttokenfromheaders() (lines 77–95) recognises only Authorization: Bearer, X-META-ACCESS-TOKEN, and X-PIPEBOARD-API-TOKEN. It does not…

Published by the source

17 Jul 2026, 18:48 UTC

Last modified by the source

23 Jul 2026, 15:11 UTC

Source last checked

26 Oct 2026, 13:49 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2v2f-mvfg-ph56

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2v2f-mvfg-ph56

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54547

Advisory: meta-ads-mcp: X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token
IDs: CVE-2026-54547, GHSA-2v2f-mvfg-ph56
Record: https://patchnext.com/advisories/cve-2026-54547 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: meta-ads-mcp 1.0.115. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI meta-ads-mcp: affected < 1.0.115; fixed in 1.0.115

## Suggested inspection (read-only)
- `python -m pip show meta-ads-mcp`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on meta-ads-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2v2f-mvfg-ph56 (OSV record GHSA-2v2f-mvfg-ph56 lists affected ranges: PyPI meta-ads-mcp >=0 <1.0.115 (fixed))
- Verified: https://github.com/advisories/GHSA-2v2f-mvfg-ph56 (GitHub-reviewed advisory GHSA-2v2f-mvfg-ph56 lists affected ranges: PyPI meta-ads-mcp >=0 <1.0.115)

Commands are suggestions: review each one before running it.