A vulnerability has been found in gomarble-ai facebook-ads-mcp-server 0.1.0. The impacted element is the function fetch_pagination_url of the file server.py. Such manipulation leads to server-side request forgery. The attack can be launched remotely. The name of the patch is 4e53875aa22e8991c2fa4a7660d86e1caba66659. Applying a patch is advised to resolve this issue.
CVE-2026-19956
Score 6.3 from GitHub Security Advisory published 2026-08-16. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity63% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
August 16, 2026
Last Modified
August 20, 2026
Advisory Details (4)
Auto-updated Aug 16, 2026GitHub - gomarble-ai/facebook-ads-mcp-server · GitHub
https://github.com/gomarble-ai/facebook-ads-mcp-server/commit 4e53875aa22e (gomarble-ai/facebook-ads-mcp-server)
Fix landed in gomarble-ai/facebook-ads-mcp-server commit 4e53875aa22e — awaiting tagged release
https://github.com/gomarble-ai/facebook-ads-mcp-server/commit/4e53875aa22e8991c2fa4a7660d86e1caba66659fix: prevent SSRF in pagination fetcher
Fix merged in gomarble-ai/facebook-ads-mcp-server PR #32 on 2026-07-20 — awaiting tagged release
https://github.com/gomarble-ai/facebook-ads-mcp-server/pull/32SSRF in fetch_pagination_url — facebook-ads-mcp-server · Issue #29 · gomarble-ai/facebook-ads-mcp-server · GitHub
https://github.com/gomarble-ai/facebook-ads-mcp-server/issues/29Vendor Advisories for CVE-2026-19956(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× 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-20 22:55 UTCEPSS rescore
- 2026-08-20 13:00 UTCGHSA enrichment
- 2026-08-19 20:18 UTCEG score recompute
- 2026-08-19 20:18 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 18:53 UTCEG score recompute
- 2026-08-18 18:53 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 17:27 UTCEG score recompute
- 2026-08-17 17:27 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 21:23 UTCEG score recompute
- 2026-08-16 20:27 UTCEG score recompute
- 2026-08-16 20:26 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-19956?
When was CVE-2026-19956 disclosed?
Is CVE-2026-19956 actively exploited?
What is the CVSS score of CVE-2026-19956?
How do I remediate CVE-2026-19956?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-19956
Is Your Infrastructure Affected by CVE-2026-19956?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.