CVE-2026-53957 json
Contentful MCP Server: export_space/import_space tools pass LLM-controlled `host`/`proxy` args to CMA client, redirecting server PAT to attacker-controlled endpoint
published 2mo ago modified last mo. also GHSA-2xhg-73j7-rrgx , EUVD-2026-78590
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
Contentful MCP Server is a Model Context Protocol server for the Contentful Management API. Prior to @contentful/mcp-server 1.7.19 and @contentful/mcp-tools 0.4.5, export_space and import_space in packages/mcp-tools/src/tools/jobs/space-to-space-migration/exportSpace.ts and packages/mcp-tools/src/tools/jobs/space-to-space-migration/importSpace.ts expose host, proxy, rawProxy, and insecure network options to LLM-controlled tool arguments and combine those options with the server's CONTENTFUL_MANAGEMENT_TOKEN. After space_to_space_migration_handler enables the migration tools, a direct MCP call or prompt injection through attacker-controlled Contentful content can redirect Contentful Management API requests and their Authorization header to an attacker-controlled host or proxy. The regular tools that use createToolClient are unaffected because those tools pin the host from server configuration. Exposure of the personal access token permits persistent out-of-band access to every Contentful space within the token's scope. This issue is fixed in @contentful/mcp-server 1.7.19 and @contentful/mcp-tools 0.4.5.
Patch / fix
- npm @contentful/mcp-server 1.7.19
- npm @contentful/mcp-tools 0.4.5
- github.com/contentful/contentful-mcp-server@fa7477e commit
- github.com/contentful/contentful-mcp-server#376 pull request
- github.com/contentful/contentful-mcp-server/releases/tag/mcp-server@1… release
- github.com/contentful/contentful-mcp-server/releases/tag/mcp-tools@0.… release
- github.com/contentful/contentful-mcp-server/releases/tag/mcp-server%4… release
- github.com/contentful/contentful-mcp-server/releases/tag/mcp-tools%40… release
Is CVE-2026-53957 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/contentful/contentful-mcp-server/security/advisories/GHSA-2xhg-73j7-rrgx referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @contentful/mcp-server | <1.7.19 |
1.7.19 |
| npm | @contentful/mcp-tools | <0.4.5 |
0.4.5 |
Affected products
- contentful contentful-mcp-server
- @contentful mcp-server
- @contentful mcp-tools
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/contentful/contentful-mcp-server/pull/376
web
-
github.com
/contentful/contentful-mcp-server/commit/fa7477ee48515f4248bc91a025eab0ca83423fe0
web
-
github.com
/contentful/contentful-mcp-server/security/advisories/GHSA-2xhg-73j7-rrgx
exploit, web
- github.com /contentful/contentful-mcp-server/releases/tag/mcp-server@1.7.19
- github.com /contentful/contentful-mcp-server/releases/tag/mcp-tools@0.4.5
-
github.com
/contentful/contentful-mcp-server
package
-
github.com
/contentful/contentful-mcp-server/releases/tag/mcp-server%401.7.19
web
-
github.com
/contentful/contentful-mcp-server/releases/tag/mcp-tools%400.4.5
web
Sources
- CVE List CVE-2026-53957
- GitHub Advisory GHSA-2xhg-73j7-rrgx
- NVD CVE-2026-53957
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.