# CVE-2026-54549: Meta Ads MCP: Server-Side Request Forgery (SSRF) in `upload_ad_image` via Unrestricted `image_url` Fetch

> Attackers can exploit SSRF in Meta Ads MCP to access internal services or cloud metadata via unrestricted image URL fetching.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-45gf-fjxp-cjpq, PYSEC-2026-3485

## What is CVE-2026-54549?

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.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-54549?

3 open source packages ship an affected version, including meta-ads-mcp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `meta-ads-mcp` | PyPI | All versions | 1.0.115 |
| `meta-ads-mcp` | PyPI | All versions | 1.0.115 |
| `meta-ads-mcp` | PyPI | All versions | 1.0.115 |

## How do I fix CVE-2026-54549?

Upgrade meta-ads-mcp to 1.0.115 or later.

## Is CVE-2026-54549 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54549 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54549 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54549 exists.

Affected packages and fixed versions:
- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.115
- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.115
- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.115

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54549/ (Markdown: https://insights.sbomify.com/CVE-2026-54549/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54549
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54549
- OSV: https://osv.dev/vulnerability/CVE-2026-54549

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54549/
Summaries are generated and may contain mistakes; the official description above is the record.