CVE-2026-54547

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-07-17. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-78886 (ENISA EUVD) · GHSA-2v2f-mvfg-ph56 (GitHub Security Advisories) · PYSEC-2026-3484 (OSV.dev)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta Ads. Prior to version 1.0.115, AuthInjectionMiddleware in meta_ads_mcp/core/http_auth_integration.py rejects HTTP MCP requests only when both auth_token and pipeboard_token are absent, while extract_token_from_headers() does not recognize X-Pipeboard-Token as a primary credential. A network caller using the streamable-http transport can therefore send any X-Pipeboard-Token value, pass the guard without establishing authentication context, and cause get_auth_token() to fall back to the server operator's META_ACCESS_TOKEN. Subsequent MCP tools execute with the operator's Meta credentials and can read or modify the operator's Meta Ads data. Deployments using the default stdio transport or without META_ACCESS_TOKEN are not affected. This issue is fixed in version 1.0.115.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 17, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

1.0.115

Patch available: pipeboard-co/meta-ads-mcp 1.0.115

https://github.com/pipeboard-co/meta-ads-mcp/releases/tag/1.0.115
GitHub commit Patch Available

commit 95e852793b7f (pipeboard-co/meta-ads-mcp)

Patch available: pipeboard-co/meta-ads-mcp 1.0.115 (contains commit 95e852793b7f)

https://github.com/pipeboard-co/meta-ads-mcp/commit/95e852793b7ff8604a8132e85d5facd08c91a36e
GitHub pull request Patch Available

fix(auth): require a primary access-token credential at the HTTP middleware (1.0.114)

Patch available: pipeboard-co/meta-ads-mcp 1.0.115 (PR #137 merged 2026-06-05)

https://github.com/pipeboard-co/meta-ads-mcp/pull/137
GitHub advisoryMentions a patch (unverified)

X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token · Advisory · pipeboard-co/meta-ads-mcp · GitHub

https://github.com/pipeboard-co/meta-ads-mcp/security/advisories/GHSA-2v2f-mvfg-ph56

Vendor Advisories for CVE-2026-54547(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipmeta-ads-mcp @ 1.0.115 (fixes < 1.0.115)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
meta-ads-mcp0.1.0 ... 1.0.99 (172 versions)
  • every version up to 1.0.115: fixed in 1.0.115
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-12 04:56 UTCEchelonGraph re-scored
  3. 2026-11-12 04:56 UTCGHSA enrichmentGHSA-2v2f-mvfg-ph56 · GitHub severity HIGH · GitHub CVSS 7.4
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-11-05 16:47 UTCEchelonGraph re-scored
  11. 2026-11-05 16:47 UTCGHSA enrichmentGHSA-2v2f-mvfg-ph56 · GitHub severity HIGH · GitHub CVSS 7.4
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-2v2f-mvfg-ph56 · GitHub severity HIGH · GitHub CVSS 7.4
  18. 2026-11-01 07:44 UTCEchelonGraph re-scored
  19. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-30 04:33 UTCEchelonGraph re-scored
  22. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 56 more
  1. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-25 14:19 UTCEchelonGraph re-scored
  3. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-23 16:24 UTCEchelonGraph re-scored
  6. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-18 03:30 UTCEchelonGraph re-scored
  12. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-17 04:10 UTCEchelonGraph re-scored
  14. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-12 15:56 UTCEchelonGraph re-scored
  20. 2026-10-11 19:39 UTCEchelonGraph re-scored
  21. 2026-10-11 16:54 UTCEchelonGraph re-scored
  22. 2026-10-11 14:18 UTCEchelonGraph re-scored
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  26. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  29. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  31. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  32. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  33. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  34. 2026-09-30 18:11 UTCEchelonGraph re-scored
  35. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  36. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  37. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  38. 2026-09-28 07:52 UTCEchelonGraph re-scored
  39. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  41. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  42. 2026-09-24 04:32 UTCEchelonGraph re-scored
  43. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  44. 2026-09-23 02:25 UTCEchelonGraph re-scored
  45. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  46. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  47. 2026-09-18 07:27 UTCEchelonGraph re-scored
  48. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-09-17 18:15 UTCEchelonGraph re-scored
  50. 2026-09-17 10:15 UTCEchelonGraph re-scored
  51. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-09-15 18:36 UTCEchelonGraph re-scored
  53. 2026-07-30 09:29 UTCEchelonGraph re-scored
  54. 2026-07-26 11:18 UTCEchelonGraph re-scored
  55. 2026-07-23 03:19 UTCEchelonGraph re-scored
  56. 2026-07-17 19:00 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-54547?
CVE-2026-54547 is a high-severity vulnerability; its CVE record was published on July 17, 2026. Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta Ads. Prior to version 1.0.115, AuthInjectionMiddleware in meta_ads_mcp/core/http_auth_integration.py rejects HTTP MCP requests only when both auth_token and pipeboard_token are absent, while…
When was the CVE record for CVE-2026-54547 published?
The CVE record for CVE-2026-54547 was published on July 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54547 actively exploited?
CVE-2026-54547 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54547?
CVE-2026-54547 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54547?
A fix for CVE-2026-54547 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54547 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54547

Explore →

Is Your Infrastructure Affected by CVE-2026-54547?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.