{
  "@id": "urn:uuid:f949fc7b-532d-4f3b-82ba-5280b82afe58",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 11,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-17T12:36:37.186666+00:00",
  "statements": [
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-08T21:22:00.146687+00:00",
      "status_notes": "Vulnerability CVE-2025-66414 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk.",
      "vulnerability": {
        "name": "CVE-2025-66414"
      },
      "action_statement": "Vulnerability CVE-2025-66414 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-17T12:36:00.088038+00:00",
      "status_notes": "Vulnerability CVE-2026-0621 does not affect version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk. not_affected \u2014 Target @modelcontextprotocol/sdk 1.30.0-tuxcare.4 already contains the upstream ReDoS fix (commit b392f02, v1.x backport). The exploded-variable regex is `([^/,]+(?:,[^/,]+)*)`, so the repeated segments and the comma separator can't overlap and there is no nested-quantifier backtracking. The fix shipped in the upstream release before the first TuxCare commit.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-0621"
      },
      "impact_statement": "not_affected \u2014 Target @modelcontextprotocol/sdk 1.30.0-tuxcare.4 already contains the upstream ReDoS fix (commit b392f02, v1.x backport). The exploded-variable regex is `([^/,]+(?:,[^/,]+)*)`, so the repeated segments and the comma separator can't overlap and there is no nested-quantifier backtracking. The fix shipped in the upstream release before the first TuxCare commit."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-11T00:40:14.375264+00:00",
      "status_notes": "Vulnerability CVE-2026-104850 is fixed in version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk.",
      "vulnerability": {
        "name": "CVE-2026-104850"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-27T11:13:37.018868+00:00",
      "status_notes": "Vulnerability CVE-2026-111767 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2026-111767"
      },
      "action_statement": "Vulnerability CVE-2026-111767 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.2."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-27T11:13:37.018868+00:00",
      "status_notes": "Vulnerability CVE-2026-111768 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2026-111768"
      },
      "action_statement": "Vulnerability CVE-2026-111768 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.2."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-27T14:08:42.105171+00:00",
      "status_notes": "Vulnerability CVE-2026-111769 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.3.",
      "vulnerability": {
        "name": "CVE-2026-111769"
      },
      "action_statement": "Vulnerability CVE-2026-111769 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.3."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-27T11:13:37.018868+00:00",
      "status_notes": "Vulnerability CVE-2026-111771 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2026-111771"
      },
      "action_statement": "Vulnerability CVE-2026-111771 affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.2."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-17T12:36:37.186666+00:00",
      "status_notes": "Vulnerability CVE-2026-25536 does not affect version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk. not_affected \u2014 The upstream fix for CVE-2026-25536 (upstream commit a05be176, authored by paulc@anthropic.com) is already in the shipped 1.30.0 release. All three guards from the advisory are present in the target. Protocol.connect() rejects a second transport, the stateless transport rejects a second handleRequest(), and in-flight handler abort controllers are aborted on close and checked before handler-extr...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-25536"
      },
      "impact_statement": "not_affected \u2014 The upstream fix for CVE-2026-25536 (upstream commit a05be176, authored by paulc@anthropic.com) is already in the shipped 1.30.0 release. All three guards from the advisory are present in the target. Protocol.connect() rejects a second transport, the stateless transport rejects a second handleRequest(), and in-flight handler abort controllers are aborted on close and checked before handler-extr..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.30.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-17T12:08:34.981060+00:00",
      "status_notes": "Vulnerability GHSA-f897-62hf-6gxq affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.4.",
      "vulnerability": {
        "name": "GHSA-f897-62hf-6gxq"
      },
      "action_statement": "Vulnerability GHSA-f897-62hf-6gxq affects version 1.30.0-tuxcare.1 of @modelcontextprotocol/sdk, and is fixed in 1.30.0-tuxcare.4."
    }
  ]
}
