Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta Ads. Prior to version 1.0.109, AuthInjectionMiddleware.dispatch() at http_auth_integration.py:272 unconditionally forwards unauthenticated Streamable HTTP requests to downstream MCP tool handlers without issuing a 401 response, allowing any network-reachable caller to invoke MCP tools without authentication. When no per-request credential is present, tool handlers fall back to the META_ACCESS_TOKEN environment variable, and when the downstream Meta Graph API call fails, api.py:263–269 serialises the raw httpx request URL—including the operator's access_token as a query parameter—into the JSON-RPC response body, delivering the credential to the unauthenticated caller. Version 1.0.109 fixes the issue.
CVE-2026-48039
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
June 11, 2026
Last Modified
August 7, 2026
Advisory Details (3)
Auto-updated Aug 7, 2026advisory-database/vulns/meta-ads-mcp/PYSEC-2026-413.yaml at main · pypa/advisory-database · GitHub
https://github.com/pypa/advisory-database/tree/main/vulns/meta-ads-mcp/PYSEC-2026-413.yaml1.0.109
Patch available: pipeboard-co/meta-ads-mcp 1.0.109
https://github.com/pipeboard-co/meta-ads-mcp/releases/tag/1.0.109Unauthenticated HTTP MCP Tool Execution Leaks Operator Meta Access Token · Advisory · pipeboard-co/meta-ads-mcp · GitHub
https://github.com/pipeboard-co/meta-ads-mcp/security/advisories/GHSA-9gw6-46qc-99vrVendor Advisories for CVE-2026-48039(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| meta-ads-mcp | 0.1.0 ... 1.0.99 (167 versions) | 1.0.109 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 32× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 00:04 UTCEG score recompute
- 2026-08-23 10:43 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 01:29 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 08:51 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:54 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 15:34 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 16:20 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 03:57 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 03:02 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-13 22:14 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 17:42 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 16:40 UTCEG score recompute
- 2026-08-11 00:03 UTCEG score recompute
Show 13 moreShow fewer
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 17:47 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 17:06 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 20:30 UTCEG score recompute
- 2026-07-30 09:41 UTCEG score recompute
- 2026-07-26 20:54 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-11 13:56 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(5)
What is CVE-2026-48039?
When was CVE-2026-48039 disclosed?
Is CVE-2026-48039 actively exploited?
What is the CVSS score of CVE-2026-48039?
How do I remediate CVE-2026-48039?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48039
Is Your Infrastructure Affected by CVE-2026-48039?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.