{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:41f4c54f-32bc-5068-8fe5-213ffb23151e",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "js-yaml",
      "purl": "pkg:npm/js-yaml@4.3.0-tuxcare.4",
      "type": "library",
      "bom-ref": "pkg:npm/js-yaml@4.3.0-tuxcare.4",
      "version": "4.3.0-tuxcare.4",
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2026-59868",
      "affects": [
        {
          "ref": "pkg:npm/js-yaml@4.3.0-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:bba5a538-cd6d-583e-b9d6-ade04b173ba6",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-59868 does not affect version 4.3.0-tuxcare.4 of js-yaml. not_affected \u2014 CVE-2026-59868 is NOT present in js-yaml v4.3.0. The upstream vendor (Vitaly Puzrin) backported the maxTotalMergeKeys defense from v5, which prevents the O(N^2) merge-chain CPU exhaustion attack. The fix is present at lib/loader.js:155,166,384-386 and enforces a cumulative limit (default 10000) on keys processed during merge operations. This is an upstream vendor fix that TuxCare's repository i..."
      }
    },
    {
      "id": "CVE-2026-59870",
      "affects": [
        {
          "ref": "pkg:npm/js-yaml@4.3.0-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:8f8ec8de-d8c5-50cf-9333-0d34c9877a4b",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-59870 is fixed in version 4.3.0-tuxcare.4 of js-yaml."
      }
    },
    {
      "id": "CVE-2026-73643",
      "affects": [
        {
          "ref": "pkg:npm/js-yaml@4.3.0-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:2cc4dca6-c2f6-5242-9733-95ca2d98c81b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-73643 does not affect version 4.3.0-tuxcare.4 of js-yaml. Version 4.3.0 is NOT affected by CVE-2026-73643. The vulnerability was introduced in version 5.0.0 when js-yaml was rewritten with a new TypeScript-based event parser. Version 4.3.0 uses the older JavaScript-based parser architecture that does not exhibit the exponential re-parsing behavior. While version 4.3.0 does process nested flow sequences with key:value pairs (the Input), its parser cannot reach the Goal (exponential CPU exhaustion) because it lacks the vulnerable code path (restoreState + re-parse pattern).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-84375",
      "affects": [
        {
          "ref": "pkg:npm/js-yaml@4.3.0-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:2365a042-8cc4-5f3a-a5ea-88e2edab4f74",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-84375 is fixed in version 4.3.0-tuxcare.4 of js-yaml."
      }
    },
    {
      "id": "GHSA-5p4m-2wfm-xmqj",
      "affects": [
        {
          "ref": "pkg:npm/js-yaml@4.3.0-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:0740ae55-fbad-5778-92eb-ce8d82ef86f1",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability GHSA-5p4m-2wfm-xmqj is fixed in version 4.3.0-tuxcare.4 of js-yaml."
      }
    },
    {
      "id": "GHSA-pm4m-ph32-ghv5",
      "affects": [
        {
          "ref": "pkg:npm/js-yaml@4.3.0-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:fc8c1893-f7a4-5d9a-9a28-8ea53a46a4b5",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability GHSA-pm4m-ph32-ghv5 does not affect version 4.3.0-tuxcare.4 of js-yaml. Version 4.3.0 uses a JavaScript direct-parsing architecture that does not exhibit the exponential reparsing vulnerability. The vulnerability exists only in v5.x's TypeScript event-based parser which uses a rewind-and-reparse pattern. Testing confirms v4.3.0 completes the CVE PoC payload (n=30) in <10ms, whereas vulnerable v5.x versions would take >2 minutes. The target architecture never had the vulnerable code path.",
        "justification": "code_not_present"
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/js-yaml@4.3.0-tuxcare.4"
    }
  ]
}