{"answers":{"affected":"3 open source packages ship an affected version, including meta-ads-mcp.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54547 exists.","fix":"Upgrade meta-ads-mcp to 1.0.115 or later.","what":"CVE-2026-54547 is a high-severity authentication bypass vulnerability in pipeboard-co meta-ads-mcp, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54547 and fix it if it is affected.\n\nWhat it is: CVE-2026-54547 is a high-severity authentication bypass vulnerability in pipeboard-co meta-ads-mcp, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54547 exists.\n\nAffected packages and fixed versions:\n- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.115\n- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.115\n- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.115\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54547/ (Markdown: https://insights.sbomify.com/CVE-2026-54547/index.md)","id":"CVE-2026-54547","markdown":"https://insights.sbomify.com/CVE-2026-54547/index.md","name":"CVE-2026-54547","record":{"aliases":["GHSA-2v2f-mvfg-ph56","PYSEC-2026-3484"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Meta Ads MCP server","requires_auth":"none","summary":"Attackers can bypass authentication by sending an X-Pipeboard-Token header, causing the server to execute actions using the operator's Meta credentials.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Meta Ads MCP: X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token","id":"CVE-2026-54547","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"kas: Persistent SSH Host Key Checking Disablement","id":"CVE-2026-54548"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.115"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":null,"source":"GHSA-2v2f-mvfg-ph56"},{"ecosystem":"PyPI","fixed":["1.0.115"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":"pkg:pypi/meta-ads-mcp","source":"GHSA-2v2f-mvfg-ph56"},{"ecosystem":"PyPI","fixed":["1.0.115"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":"pkg:pypi/meta-ads-mcp","source":"PYSEC-2026-3484"}],"prev":{"headline":"CloudTAK: Authenticated full-read SSRF in CloudTAK basemap import (PUT /api/basemap) — no IP-classification guard","id":"CVE-2026-54546"},"products":["meta-ads-mcp"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["pipeboard-co"]},"summary":"Attackers can bypass authentication by sending an X-Pipeboard-Token header, causing the server to execute actions using the operator's Meta credentials.","url":"https://insights.sbomify.com/CVE-2026-54547/"}