{
  "@id": "urn:uuid:279ef875-4457-403b-b4b4-de8ca7d5f2fc",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-09-24T09:31:26.931840+00:00",
  "statements": [
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-64718 is fixed in version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "CVE-2025-64718"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-53550 is fixed in version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "CVE-2026-53550"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-59868 affects version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "CVE-2026-59868"
      },
      "action_statement": "Vulnerability CVE-2026-59868 affects version 3.3.1-tuxcare.3 of js-yaml."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-59869 is fixed in version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "CVE-2026-59869"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-59870 affects version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "CVE-2026-59870"
      },
      "action_statement": "Vulnerability CVE-2026-59870 affects version 3.3.1-tuxcare.3 of js-yaml."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-73643 does not affect version 3.3.1-tuxcare.3 of js-yaml. CVE-2026-73643 describes an exponential parsing vulnerability affecting js-yaml versions 5.0.0-5.2.2 where nested flow sequences used as keys cause O(2^n) re-parsing via restoreState. Target version 3.3.1 predates the TypeScript rewrite (v5.0.0) where this vulnerability was introduced. The JavaScript implementation in 3.3.1 parses flow collections linearly without state restoration or re-parsing mechanisms. Empirical testing with nested flow sequences up to depth 60 confirms linear performance (<1ms) with no exponential behavior. The vulnerability pattern was introduced in version 5.0.0 and fixed in 5.2.2 (commit 3e5240f), but version 3.3.1 never contained the vulnerable code path.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-73643"
      },
      "impact_statement": "CVE-2026-73643 describes an exponential parsing vulnerability affecting js-yaml versions 5.0.0-5.2.2 where nested flow sequences used as keys cause O(2^n) re-parsing via restoreState. Target version 3.3.1 predates the TypeScript rewrite (v5.0.0) where this vulnerability was introduced. The JavaScript implementation in 3.3.1 parses flow collections linearly without state restoration or re-parsing mechanisms. Empirical testing with nested flow sequences up to depth 60 confirms linear performance (<1ms) with no exponential behavior. The vulnerability pattern was introduced in version 5.0.0 and fixed in 5.2.2 (commit 3e5240f), but version 3.3.1 never contained the vulnerable code path."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-84375 is fixed in version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "CVE-2026-84375"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability GHSA-2pr6-76vf-7546 is fixed in version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "GHSA-2pr6-76vf-7546"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability GHSA-5p4m-2wfm-xmqj is fixed in version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "GHSA-5p4m-2wfm-xmqj"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability GHSA-8j8c-7jfh-h6hx is fixed in version 3.3.1-tuxcare.3 of js-yaml.",
      "vulnerability": {
        "name": "GHSA-8j8c-7jfh-h6hx"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@3.3.1-tuxcare.3",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@3.3.1-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability GHSA-pm4m-ph32-ghv5 does not affect version 3.3.1-tuxcare.3 of js-yaml. not_affected \u2014 Version 3.3.1 (released 2015-05-13) does not contain the exponential-time parsing vulnerability. The vulnerable pattern (parser rewind + re-parsing of flow sequence keys) was introduced in later versions during a refactor to TypeScript and event-based parsing. Version 3.3.1 uses a fundamentally different architecture that parses each node exactly once, achieving O(n) complexity instead of O(2^n).",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "GHSA-pm4m-ph32-ghv5"
      },
      "impact_statement": "not_affected \u2014 Version 3.3.1 (released 2015-05-13) does not contain the exponential-time parsing vulnerability. The vulnerable pattern (parser rewind + re-parsing of flow sequence keys) was introduced in later versions during a refactor to TypeScript and event-based parsing. Version 3.3.1 uses a fundamentally different architecture that parses each node exactly once, achieving O(n) complexity instead of O(2^n)."
    }
  ]
}