{
  "@id": "urn:uuid:f69d4756-5598-47d2-9216-92e2e697a2c5",
  "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": "affected",
      "products": [
        {
          "@id": "pkg:npm/tough-cookie@2.2.0",
          "identifiers": {
            "purl": "pkg:npm/tough-cookie@2.2.0"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2016-1000232 affects version 2.2.0 of tough-cookie, and is fixed in 2.2.0-tuxcare.1.",
      "vulnerability": {
        "name": "CVE-2016-1000232"
      },
      "action_statement": "Vulnerability CVE-2016-1000232 affects version 2.2.0 of tough-cookie, and is fixed in 2.2.0-tuxcare.1."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/tough-cookie@2.2.0",
          "identifiers": {
            "purl": "pkg:npm/tough-cookie@2.2.0"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2017-15010 affects version 2.2.0 of tough-cookie, and is fixed in 2.2.0-tuxcare.1.",
      "vulnerability": {
        "name": "CVE-2017-15010"
      },
      "action_statement": "Vulnerability CVE-2017-15010 affects version 2.2.0 of tough-cookie, and is fixed in 2.2.0-tuxcare.1."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/tough-cookie@2.2.0",
          "identifiers": {
            "purl": "pkg:npm/tough-cookie@2.2.0"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2017-16137 is a false positive for tough-cookie 2.2.0. false_positive \u2014 CVE-2017-16137 is not applicable to this repository. The CVE concerns the 'debug' npm package (a logging utility), while the target repository is 'tough-cookie' (an RFC6265 cookie parsing library). The affected component is absent from the entire repository - no vendored copy, no dependency relationship, and no code usage.",
      "vulnerability": {
        "name": "CVE-2017-16137"
      },
      "impact_statement": "false_positive \u2014 CVE-2017-16137 is not applicable to this repository. The CVE concerns the 'debug' npm package (a logging utility), while the target repository is 'tough-cookie' (an RFC6265 cookie parsing library). The affected component is absent from the entire repository - no vendored copy, no dependency relationship, and no code usage."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/tough-cookie@2.2.0",
          "identifiers": {
            "purl": "pkg:npm/tough-cookie@2.2.0"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2017-20165 is a false positive for tough-cookie 2.2.0. false_positive \u2014 CVE-2017-20165 concerns the debug-js/debug library, not the tough-cookie library. This is a wrong-project match with no relationship between the affected component and this repository.",
      "vulnerability": {
        "name": "CVE-2017-20165"
      },
      "impact_statement": "false_positive \u2014 CVE-2017-20165 concerns the debug-js/debug library, not the tough-cookie library. This is a wrong-project match with no relationship between the affected component and this repository."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/tough-cookie@2.2.0",
          "identifiers": {
            "purl": "pkg:npm/tough-cookie@2.2.0"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2023-26136 affects version 2.2.0 of tough-cookie, and is fixed in 2.2.0-tuxcare.1.",
      "vulnerability": {
        "name": "CVE-2023-26136"
      },
      "action_statement": "Vulnerability CVE-2023-26136 affects version 2.2.0 of tough-cookie, and is fixed in 2.2.0-tuxcare.1."
    }
  ]
}