{
  "@id": "urn:uuid:1458b139-5c61-40aa-8aa5-6e9027b5a6b9",
  "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/qs@2.4.2-tuxcare.2",
          "identifiers": {
            "purl": "pkg:npm/qs@2.4.2-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2017-1000048 is fixed in version 2.4.2-tuxcare.2 of qs.",
      "vulnerability": {
        "name": "CVE-2017-1000048"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.4.2-tuxcare.2",
          "identifiers": {
            "purl": "pkg:npm/qs@2.4.2-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2022-24999 affects version 2.4.2-tuxcare.2 of qs, and is fixed in 2.4.2-tuxcare.3.",
      "vulnerability": {
        "name": "CVE-2022-24999"
      },
      "action_statement": "Vulnerability CVE-2022-24999 affects version 2.4.2-tuxcare.2 of qs, and is fixed in 2.4.2-tuxcare.3."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.4.2-tuxcare.2",
          "identifiers": {
            "purl": "pkg:npm/qs@2.4.2-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-15284 affects version 2.4.2-tuxcare.2 of qs, and is fixed in 2.4.2-tuxcare.3.",
      "vulnerability": {
        "name": "CVE-2025-15284"
      },
      "action_statement": "Vulnerability CVE-2025-15284 affects version 2.4.2-tuxcare.2 of qs, and is fixed in 2.4.2-tuxcare.3."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.4.2-tuxcare.2",
          "identifiers": {
            "purl": "pkg:npm/qs@2.4.2-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-2391 does not affect version 2.4.2-tuxcare.2 of qs. Version 2.4.2 is not vulnerable. Summary: Target repository (qs v2.4.2) does not contain the 'comma' option feature required for CVE-2026-2391 exploitation. This vulnerability only affects qs versions 6.x and later where the comma-separated value parsing feature exists. [terminalized not_affected from patch_application_manual/not_vulnerable]",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-2391"
      },
      "impact_statement": "Version 2.4.2 is not vulnerable. Summary: Target repository (qs v2.4.2) does not contain the 'comma' option feature required for CVE-2026-2391 exploitation. This vulnerability only affects qs versions 6.x and later where the comma-separated value parsing feature exists. [terminalized not_affected from patch_application_manual/not_vulnerable]"
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.4.2-tuxcare.2",
          "identifiers": {
            "purl": "pkg:npm/qs@2.4.2-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-82417 affects version 2.4.2-tuxcare.2 of qs.",
      "vulnerability": {
        "name": "CVE-2026-82417"
      },
      "action_statement": "Vulnerability CVE-2026-82417 affects version 2.4.2-tuxcare.2 of qs."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.4.2-tuxcare.2",
          "identifiers": {
            "purl": "pkg:npm/qs@2.4.2-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-82562 does not affect version 2.4.2-tuxcare.2 of qs. not_affected \u2014 Target version 2.4.2 is not affected by CVE-2026-82562. The vulnerability requires the comma parsing feature (`comma: true` option) which was introduced in qs v6.7.0. Version 2.4.2 predates this feature by many major releases and does not process comma-separated values in query strings. Testing confirms the comma option is ignored - `a[]=1,2,3,4` remains a single string value rather than being ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-82562"
      },
      "impact_statement": "not_affected \u2014 Target version 2.4.2 is not affected by CVE-2026-82562. The vulnerability requires the comma parsing feature (`comma: true` option) which was introduced in qs v6.7.0. Version 2.4.2 predates this feature by many major releases and does not process comma-separated values in query strings. Testing confirms the comma option is ignored - `a[]=1,2,3,4` remains a single string value rather than being ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.4.2-tuxcare.2",
          "identifiers": {
            "purl": "pkg:npm/qs@2.4.2-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-8723 does not affect version 2.4.2-tuxcare.2 of qs. not_affected \u2014 Target version 2.4.2 is not affected by CVE-2026-8723. The vulnerability was introduced in v6.11.1 (2023) when `arrayFormat: 'comma'` with `encodeValuesOnly` support was added. Version 2.4.2 (2015) predates this feature and does not contain the vulnerable code path. The `utils.maybeMap(obj, encoder)` call that crashes on null/undefined does not exist in v2.4.2. Additionally, v2.4.2 has explicit...",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2026-8723"
      },
      "impact_statement": "not_affected \u2014 Target version 2.4.2 is not affected by CVE-2026-8723. The vulnerability was introduced in v6.11.1 (2023) when `arrayFormat: 'comma'` with `encodeValuesOnly` support was added. Version 2.4.2 (2015) predates this feature and does not contain the vulnerable code path. The `utils.maybeMap(obj, encoder)` call that crashes on null/undefined does not exist in v2.4.2. Additionally, v2.4.2 has explicit..."
    }
  ]
}