{
  "@id": "urn:uuid:42e50758-927c-4488-a6a8-25c6e4f11cdf",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 2,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-10-03T10:13:00.652366+00:00",
  "statements": [
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@4.3.1",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@4.3.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-59868 affects version 4.3.1 of js-yaml.",
      "vulnerability": {
        "name": "CVE-2026-59868"
      },
      "action_statement": "Vulnerability CVE-2026-59868 affects version 4.3.1 of js-yaml."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@4.3.1",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@4.3.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-59870 does not affect version 4.3.1 of js-yaml. not_affected \u2014 Target js-yaml 4.3.1-tuxcare.2 is NOT affected by CVE-2026-59870. The O(n\u00b2) algorithmic complexity vulnerability in `!!omap` duplicate key detection was fixed by upstream commit c3cc4b0 (authored by Vitaly Puzrin on 2026-07-31), which is present in the target. The fix replaced Array.indexOf() O(n) scanning with Object property O(1) lookup, eliminating the quadratic complexity. This is an upstre...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-59870"
      },
      "impact_statement": "not_affected \u2014 Target js-yaml 4.3.1-tuxcare.2 is NOT affected by CVE-2026-59870. The O(n\u00b2) algorithmic complexity vulnerability in `!!omap` duplicate key detection was fixed by upstream commit c3cc4b0 (authored by Vitaly Puzrin on 2026-07-31), which is present in the target. The fix replaced Array.indexOf() O(n) scanning with Object property O(1) lookup, eliminating the quadratic complexity. This is an upstre..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@4.3.1",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@4.3.1"
          }
        }
      ],
      "timestamp": "2026-10-03T10:13:00.652366+00:00",
      "status_notes": "Vulnerability CVE-2026-73643 does not affect version 4.3.1 of js-yaml. Version 4.3.1 is NOT AFFECTED by CVE-2026-73643. The exponential parsing vulnerability was introduced in version 5.0.0's TypeScript rewrite and does not exist in version 4.3.1's JavaScript codebase. The vulnerable pattern (restoreState + re-parseNode in readFlowCollection when flow sequence keys are detected) is absent. Version 4.3.1 uses forward-only parsing with linear time complexity, confirmed through code analysis and empirical testing (0-2ms across nesting depths 5-25). The CVE's version range \"5.0.0 until 5.2.2\" accurately excludes version 4.x.",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2026-73643"
      },
      "impact_statement": "Version 4.3.1 is NOT AFFECTED by CVE-2026-73643. The exponential parsing vulnerability was introduced in version 5.0.0's TypeScript rewrite and does not exist in version 4.3.1's JavaScript codebase. The vulnerable pattern (restoreState + re-parseNode in readFlowCollection when flow sequence keys are detected) is absent. Version 4.3.1 uses forward-only parsing with linear time complexity, confirmed through code analysis and empirical testing (0-2ms across nesting depths 5-25). The CVE's version range \"5.0.0 until 5.2.2\" accurately excludes version 4.x."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@4.3.1",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@4.3.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-84375 affects version 4.3.1 of js-yaml.",
      "vulnerability": {
        "name": "CVE-2026-84375"
      },
      "action_statement": "Vulnerability CVE-2026-84375 affects version 4.3.1 of js-yaml."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/js-yaml@4.3.1",
          "identifiers": {
            "purl": "pkg:npm/js-yaml@4.3.1"
          }
        }
      ],
      "timestamp": "2026-10-03T10:13:00.652366+00:00",
      "status_notes": "Vulnerability GHSA-pm4m-ph32-ghv5 does not affect version 4.3.1 of js-yaml. The target (js-yaml v4.3.1-tuxcare.2) is not affected by GHSA-pm4m-ph32-ghv5. This exponential parsing vulnerability was introduced and fixed in the v5.x branch (commit 3e5240f, released in v5.2.2), which uses a completely rewritten TypeScript event-based parser architecture. The v4.3.1 codebase uses the legacy JavaScript composition-based parser that does not contain the vulnerable code pattern (restoreState + parseNode reparsing). The v4.x architecture parses flow sequence elements exactly once per nesting level with no exponential reparsing behavior.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "GHSA-pm4m-ph32-ghv5"
      },
      "impact_statement": "The target (js-yaml v4.3.1-tuxcare.2) is not affected by GHSA-pm4m-ph32-ghv5. This exponential parsing vulnerability was introduced and fixed in the v5.x branch (commit 3e5240f, released in v5.2.2), which uses a completely rewritten TypeScript event-based parser architecture. The v4.3.1 codebase uses the legacy JavaScript composition-based parser that does not contain the vulnerable code pattern (restoreState + parseNode reparsing). The v4.x architecture parses flow sequence elements exactly once per nesting level with no exponential reparsing behavior."
    }
  ]
}