{"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-48039 exists.","fix":"Upgrade meta-ads-mcp to 1.0.109 or later.","what":"CVE-2026-48039 is a critical authentication bypass vulnerability in pipeboard-co meta-ads-mcp, published on 7 Aug 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-48039 and fix it if it is affected.\n\nWhat it is: CVE-2026-48039 is a critical authentication bypass vulnerability in pipeboard-co meta-ads-mcp, published on 7 Aug 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-48039 exists.\n\nAffected packages and fixed versions:\n- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.109\n- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.109\n- meta-ads-mcp (PyPI): affected all versions; fixed in 1.0.109\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-48039/ (Markdown: https://insights.sbomify.com/CVE-2026-48039/index.md)","id":"CVE-2026-48039","markdown":"https://insights.sbomify.com/CVE-2026-48039/index.md","name":"CVE-2026-48039","record":{"aliases":["GHSA-9gw6-46qc-99vr","PYSEC-2026-413"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Meta Ads MCP server","requires_auth":"none","summary":"Unauthenticated attackers can invoke MCP tools and leak the operator's Meta access token due to missing authentication checks and verbose error handling.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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.","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: Unauthenticated HTTP MCP Tool Execution Leaks Operator Meta Access Token","id":"CVE-2026-48039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"netty-incubator-codec-ohttp's Incorrect Native Pointer Derivation in Pooled Direct ByteBuf Fallback Leads to Out-of-Bounds Native Memory Access","id":"CVE-2026-48040"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.109"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":null,"source":"GHSA-9gw6-46qc-99vr"},{"ecosystem":"PyPI","fixed":["1.0.109"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":"pkg:pypi/meta-ads-mcp","source":"GHSA-9gw6-46qc-99vr"},{"ecosystem":"PyPI","fixed":["1.0.109"],"introduced":["0"],"last_affected":[],"package":"meta-ads-mcp","purl":"pkg:pypi/meta-ads-mcp","source":"PYSEC-2026-413"}],"prev":{"headline":"joi: Uncaught RangeError on deeply nested input through recursive `link()` schemas","id":"CVE-2026-48038"},"products":["meta-ads-mcp"],"published":"2026-08-07","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":"total"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["pipeboard-co"]},"summary":"Unauthenticated attackers can invoke MCP tools and leak the operator's Meta access token due to missing authentication checks and verbose error handling.","url":"https://insights.sbomify.com/CVE-2026-48039/"}