← Back
CVE-2026-53957
SSRF (Server-Side Request Forgery) in @contentful/mcp-server (CVE-2026-53957)
Summary
SSRF in @contentful/mcp-server (CVE-2026-53957). Risk of unauthorized operations or information disclosure. Exploitable via ``export_space``. Mitigation: upgrade to `1.7.19` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53957** has been found in @contentful/mcp-server.
Attackers can target a specific entry point like ``export_space`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @contentful/mcp-server to **1.7.19** or later.
If unsure, ask your IT team or search "@contentful/mcp-server CVE-2026-53957" on the vendor's site.
CVE-2026-53957 (@contentful/mcp-server) — CWE-918 /
Attack surface: `export_space` / `import_space` / `host` / `proxy`
Patched: `1.7.19` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in @contentful/mcp-server. Attackers reach the vulnerable code path via ``export_space`` without authentication.
📍 Affected scope
@contentful/mcp-server — . Attack surface: `export_space` / `import_space` / `host` / `proxy`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.7.19**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@contentful/mcp-server' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@contentful/mcp-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@contentful/mcp-server` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @contentful/mcp-server to 1.7.19ステージング環境で 1.7.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@contentful/mcp-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.19"}]}]
npm
@contentful/mcp-tools
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.5"}]}]
References
- web https://github.com/contentful/contentful-mcp-server/security/advisories/GHSA-2xhg-73j7-rrgx
- web https://github.com/contentful/contentful-mcp-server/pull/376
- web https://github.com/contentful/contentful-mcp-server/commit/fa7477ee48515f4248bc91a025eab0ca83423fe0
- web https://github.com/contentful/contentful-mcp-server/releases/tag/mcp-server%401.7.19
- web https://github.com/contentful/contentful-mcp-server/releases/tag/mcp-tools%400.4.5
- web https://github.com/advisories/GHSA-2xhg-73j7-rrgx