中危
@modelcontextprotocol/sdk
CVE-2026-111767
MCP TypeScript SDK: Experimental tasks were not tied to the session that created them
暂无修复版本
中危
@modelcontextprotocol/sdk
CVE-2026-25536
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
暂无修复版本
中危
@modelcontextprotocol/sdk
CVE-2026-111768
MCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation
暂无修复版本
中危
@modelcontextprotocol/sdk
CVE-2026-111769
MCP TypeScript client SDK: HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodies
暂无修复版本
中危
@modelcontextprotocol/sdk
CVE-2026-104850
MCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server
暂无修复版本
中危
@modelcontextprotocol/sdk
GHSA-f897-62hf-6gxq
MCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length
暂无修复版本
中危
js-yaml
CVE-2026-84375
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
暂无修复版本
中危
js-yaml
CVE-2026-59869
js-yaml: YAML merge-key chains can force quadratic CPU consumption
暂无修复版本
中危
js-yaml
GHSA-5p4m-2wfm-xmqj
JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported
暂无修复版本
低危
js-yaml
CVE-2026-53550
JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases
暂无修复版本
低危
js-yaml
CVE-2025-64718
js-yaml has prototype pollution in merge (<<)
暂无修复版本
低危
js-yaml
GHSA-r3ph-w7gj-g6xm
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
暂无修复版本
严重
@modelcontextprotocol/sdk
CVE-2026-111771
MCP TypeScript SDK: Server bearer authentication accepted tokens issued for another service
暂无修复版本
—
@modelcontextprotocol/sdk
CVE-2026-0621
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
暂无修复版本
—
@modelcontextprotocol/sdk
CVE-2025-66414
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
暂无修复版本
查询的是依赖声明范围的下界,不是实际安装版本;若解析到修复版本则不受影响——所以这是「可能受影响」,不是「这个插件有漏洞」。数据来自 OSV.dev。