{
  "@id": "urn:uuid:c40aa62b-3a5f-49dd-bdb9-430a151dd1fb",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 7,
  "@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.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-08T21:22:00.146687+00:00",
      "status_notes": "Vulnerability CVE-2025-66414 affects version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk.",
      "vulnerability": {
        "name": "CVE-2025-66414"
      },
      "action_statement": "Vulnerability CVE-2025-66414 affects version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-17T12:34:53.242026+00:00",
      "status_notes": "Vulnerability CVE-2026-0621 does not affect version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk. not_affected \u2014 Not affected. src/shared/uriTemplate.ts already has the upstream ReDoS fix (b392f02f, authored by paulcarletonjr@gmail.com, committed by GitHub). Exploded variables use the unambiguous pattern ([^/,]+(?:,[^/,]+)*) instead of the vulnerable ([^/]+(?:,[^/]+)*). The fix is in HEAD and was already in the history before the first TuxCare commit (59b07516). Length limits are also present.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-0621"
      },
      "impact_statement": "not_affected \u2014 Not affected. src/shared/uriTemplate.ts already has the upstream ReDoS fix (b392f02f, authored by paulcarletonjr@gmail.com, committed by GitHub). Exploded variables use the unambiguous pattern ([^/,]+(?:,[^/,]+)*) instead of the vulnerable ([^/]+(?:,[^/]+)*). The fix is in HEAD and was already in the history before the first TuxCare commit (59b07516). Length limits are also present."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-27T12:02:15.291965+00:00",
      "status_notes": "Vulnerability CVE-2026-104850 is fixed in version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk.",
      "vulnerability": {
        "name": "CVE-2026-104850"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-27T12:02:15.291965+00:00",
      "status_notes": "Vulnerability CVE-2026-111767 is fixed in version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk.",
      "vulnerability": {
        "name": "CVE-2026-111767"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-27T12:02:15.291965+00:00",
      "status_notes": "Vulnerability CVE-2026-111768 is fixed in version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk.",
      "vulnerability": {
        "name": "CVE-2026-111768"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-27T12:02:15.291965+00:00",
      "status_notes": "Vulnerability CVE-2026-111769 is fixed in version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk.",
      "vulnerability": {
        "name": "CVE-2026-111769"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-05T15:10:59.002028+00:00",
      "status_notes": "Vulnerability CVE-2026-111771 affects version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk, and is fixed in 1.26.0-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2026-111771"
      },
      "action_statement": "Vulnerability CVE-2026-111771 affects version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk, and is fixed in 1.26.0-tuxcare.4."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-17T12:36:37.186666+00:00",
      "status_notes": "Vulnerability CVE-2026-25536 does not affect version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk. not_affected \u2014 The target (1.26.0 tuxcare.5) already contains all three guards from the upstream CVE-2026-25536 fix: Protocol.connect() throws if already connected, a stateless transport's handleRequest() throws on reuse, and in-flight handler abort controllers are aborted on close and checked before sending. The fix is upstream commit a05be176 by paulc@anthropic.com, which is in the upstream 1.26.0 release b...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-25536"
      },
      "impact_statement": "not_affected \u2014 The target (1.26.0 tuxcare.5) already contains all three guards from the upstream CVE-2026-25536 fix: Protocol.connect() throws if already connected, a stateless transport's handleRequest() throws on reuse, and in-flight handler abort controllers are aborted on close and checked before sending. The fix is upstream commit a05be176 by paulc@anthropic.com, which is in the upstream 1.26.0 release b..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/%40modelcontextprotocol/sdk@1.26.0-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-17T12:33:00.040714+00:00",
      "status_notes": "Vulnerability GHSA-f897-62hf-6gxq affects version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk, and is fixed in 1.26.0-tuxcare.5.",
      "vulnerability": {
        "name": "GHSA-f897-62hf-6gxq"
      },
      "action_statement": "Vulnerability GHSA-f897-62hf-6gxq affects version 1.26.0-tuxcare.3 of @modelcontextprotocol/sdk, and is fixed in 1.26.0-tuxcare.5."
    }
  ]
}
