{"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-54549 exists.","fix":"Upgrade meta-ads-mcp to 1.0.115 or later.","what":"CVE-2026-54549 is a high-severity server-side request forgery 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-54549 and fix it if it is affected.\n\nWhat it is: CVE-2026-54549 is a high-severity server-side request forgery 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-54549 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-54549/ (Markdown: https://insights.sbomify.com/CVE-2026-54549/index.md)","id":"CVE-2026-54549","markdown":"https://insights.sbomify.com/CVE-2026-54549/index.md","name":"CVE-2026-54549","record":{"aliases":["GHSA-45gf-fjxp-cjpq","PYSEC-2026-3485"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Meta Ads MCP server","requires_auth":"none","summary":"Attackers can exploit SSRF in Meta Ads MCP to access internal services or cloud metadata via unrestricted image URL fetching.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta Ads. Prior to version 1.0.115, the upload_ad_image tool in meta_ads_mcp/core/ads.py passes an attacker-controlled image_url to try_multiple_download_methods() in meta_ads_mcp/core/utils.py, where httpx.AsyncClient uses follow_redirects=True and performs HTTP requests without validating the scheme, host, or resolved IP address. In a streamable-http deployment, a network caller can use any non-empty authorization value because Meta credential validation occurs after the image download, then direct the server to loopback services, private-network addresses, cloud metadata endpoints, or redirect-chained internal targets. The resulting server-side request forgery can expose internal data, invoke state-changing internal services, or disrupt reachable services. 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: Server-Side Request Forgery (SSRF) in `upload_ad_image` via Unrestricted `image_url` Fetch","id":"CVE-2026-54549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"IzPack has Path Traversal in UnpackerBase that allows writing files outside the installation directory via malicious pack entries","id":"CVE-2026-54550"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.115"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":null,"source":"GHSA-45gf-fjxp-cjpq"},{"ecosystem":"PyPI","fixed":["1.0.115"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":"pkg:pypi/meta-ads-mcp","source":"GHSA-45gf-fjxp-cjpq"},{"ecosystem":"PyPI","fixed":["1.0.115"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":"pkg:pypi/meta-ads-mcp","source":"PYSEC-2026-3485"}],"prev":{"headline":"kas: Persistent SSH Host Key Checking Disablement","id":"CVE-2026-54548"},"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["pipeboard-co"]},"summary":"Attackers can exploit SSRF in Meta Ads MCP to access internal services or cloud metadata via unrestricted image URL fetching.","url":"https://insights.sbomify.com/CVE-2026-54549/"}