Typescript Sdk
Approved changes feed: RSS · Atom
cpe:2.3:a:modelcontextprotocol:typescript-sdk:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Modelcontextprotocol (082e8d84-965b-5156-ba15-e7a9bafb2a96) |
|---|---|
| Product | Typescript Sdk (3a451b11-c0cd-5715-ad90-d16e6bf9b963) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-25536 |
vulnerable | 2026-06-08 07:53:19.960312 |
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
HIGH (7.1)
MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. From version 1.10.0 to 1.25.3, cross-client response data leak when a single McpServer/Server and transport instance is reused across multiple client connections, most commonly in stateless StreamableHTTPServerTransport deployments. This issue has been patched in version 1.26.0.
Published: 2026-02-04T21:29:38.276Z
Updated: 2026-06-30T03:17:05.800Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-66414 |
vulnerable | 2026-06-08 07:41:18.894402 |
DNS Rebinding Protection Disabled by Default in Model Context Protocol TypeScript SDK for Servers Running on Localhost
MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. Prior to 1.24.0, The Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default for HTTP-based servers. When an HTTP-based MCP server is run on localhost without authentication with StreamableHTTPServerTransport or SSEServerTransport and has not enabled enableDnsRebindingProtection, a malicious website could exploit DNS rebinding to bypass same-origin policy restrictions and send requests to the local MCP server. This could allow an attacker to invoke tools or access resources exposed by the MCP server on behalf of the user in those limited circumstances. Note that running HTTP-based MCP servers locally without authentication is not recommended per MCP security best practices. This issue does not affect servers using stdio transport. This vulnerability is fixed in 1.24.0.
Published: 2025-12-02T18:12:29.848Z
Updated: 2025-12-02T18:46:02.374Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.