CVE-2026-48039: pipeboard-co meta-ads-mcp · Improper Authentication
Affects pipeboard-co meta-ads-mcpSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.0.109 as a priority.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.109
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade meta-ads-mcp and pipeboard-co/meta-ads-mcp to 1.0.109.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pipeboard-cometa-ads-mcp | Affected
| Fixed in
|
GitHubpipeboard-co/meta-ads-mcppkg:github/pipeboard-co/meta-ads-mcpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to meta-ads-mcp version 1.0.109 or later, where this authentication bypass and credential leakage vulnerability is fixed. Patch status is not explicitly confirmed in the vendor advisory, but the description states version 1.0.109 fixes the issue. Until upgraded, restrict network access to the MCP server to trusted parties only.
Description
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.