meta-ads-mcp: Server-Side Request Forgery (SSRF) in upload_ad_image via Unrestricted image_url Fetch
CVE-2026-54549GHSA-45gf-fjxp-cjpq
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (meta-ads-mcp 1.0.115), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI meta-ads-mcp
- Affected
- < 1.0.115
- Fixed in
- 1.0.115
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-45gf-fjxp-cjpq lists affected ranges: PyPI meta-ads-mcp >=0 <1.0.115 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-45gf-fjxp-cjpq lists affected ranges: PyPI meta-ads-mcp >=0 <1.0.115
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
- EPSS
- CVE-2026-54549: 0.40% estimated exploitation activity in the next 30 days; percentile 34.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Server-Side Request Forgery (SSRF) in uploadadimage via Unrestricted imageurl Fetch Summary The uploadadimage MCP tool in meta-ads-mcp v1.0.113 passes an attacker-controlled imageurl parameter directly to an HTTP fetch helper (httpx.AsyncClient(followredirects=True).get(url)) without any scheme, host, or IP address validation. When the server is deployed with the streamable-http transport (a documented, officially supported mode), an unauthenticated remote attacker can supply an arbitrary URL—including http://127.0.0.1/, RFC 1918 addresses, or cloud metadata endpoints such as http://169.254.169.254/—and cause the server to issue an outbound HTTP request to that target. The Authorization middleware only verifies that a non-empty Bearer token is present; actual Meta API credential validation occurs after the image download, so any dummy Bearer token bypasses the pre-fetch check. This constitutes a full, unauthenticated Server-Side Request Forgery with a confirmed CVSS 3.1 Base Score of…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-45gf-fjxp-cjpq
- Revision 1 · created ·
Published from osv record GHSA-45gf-fjxp-cjpq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-54549 Advisory: meta-ads-mcp: Server-Side Request Forgery (SSRF) in `upload_ad_image` via Unrestricted `image_url` Fetch IDs: CVE-2026-54549, GHSA-45gf-fjxp-cjpq Record: https://patchnext.com/advisories/cve-2026-54549 (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 8.3) 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-45gf-fjxp-cjpq (OSV record GHSA-45gf-fjxp-cjpq lists affected ranges: PyPI meta-ads-mcp >=0 <1.0.115 (fixed)) - Verified: https://github.com/advisories/GHSA-45gf-fjxp-cjpq (GitHub-reviewed advisory GHSA-45gf-fjxp-cjpq lists affected ranges: PyPI meta-ads-mcp >=0 <1.0.115) Commands are suggestions: review each one before running it.
Loading voting…