{
  "@id": "urn:uuid:82ba5155-ad7d-4754-9147-575fcbc8ac8c",
  "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.2.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@2.2.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2017-1000048 is fixed in version 2.2.4-tuxcare.1 of qs.",
      "vulnerability": {
        "name": "CVE-2017-1000048"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.2.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@2.2.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2022-24999 affects version 2.2.4-tuxcare.1 of qs, and is fixed in 2.2.4-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2022-24999"
      },
      "action_statement": "Vulnerability CVE-2022-24999 affects version 2.2.4-tuxcare.1 of qs, and is fixed in 2.2.4-tuxcare.2."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/qs@2.2.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@2.2.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-15284 is fixed in version 2.2.4-tuxcare.1 of qs.",
      "vulnerability": {
        "name": "CVE-2025-15284"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.2.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@2.2.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-2391 does not affect version 2.2.4-tuxcare.1 of qs. not_affected \u2014 Version 2.2.4 does not contain the comma parsing feature required for CVE-2026-2391. The vulnerability exploits the comma option to bypass arrayLimit, but this option does not exist in version 2.2.4. Comma-separated values are treated as plain strings, not parsed into arrays.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-2391"
      },
      "impact_statement": "not_affected \u2014 Version 2.2.4 does not contain the comma parsing feature required for CVE-2026-2391. The vulnerability exploits the comma option to bypass arrayLimit, but this option does not exist in version 2.2.4. Comma-separated values are treated as plain strings, not parsed into arrays."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.2.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@2.2.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-82562 does not affect version 2.2.4-tuxcare.1 of qs. not_affected \u2014 Version 2.2.4 is not affected by CVE-2026-82562. The vulnerability requires the `comma: true` parsing option, which enables splitting comma-separated values (e.g., `a[]=1,2,3,4`) into arrays. This feature was introduced in qs v6.7.0 (commit b84acba, ~2017). Version 2.2.4 (2014) predates this feature by several years and contains no comma-parsing logic. The target receives query strings that may...",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2026-82562"
      },
      "impact_statement": "not_affected \u2014 Version 2.2.4 is not affected by CVE-2026-82562. The vulnerability requires the `comma: true` parsing option, which enables splitting comma-separated values (e.g., `a[]=1,2,3,4`) into arrays. This feature was introduced in qs v6.7.0 (commit b84acba, ~2017). Version 2.2.4 (2014) predates this feature by several years and contains no comma-parsing logic. The target receives query strings that may..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@2.2.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@2.2.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-8723 does not affect version 2.2.4-tuxcare.1 of qs. not_affected \u2014 Version 2.2.4 is not affected by CVE-2026-8723. The vulnerable code path (arrayFormat: 'comma' + encodeValuesOnly branch) does not exist in this version. The CVE explicitly states the vulnerability was introduced in v6.11.1, and version 2.2.4 predates this by many major versions with a completely different implementation architecture.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-8723"
      },
      "impact_statement": "not_affected \u2014 Version 2.2.4 is not affected by CVE-2026-8723. The vulnerable code path (arrayFormat: 'comma' + encodeValuesOnly branch) does not exist in this version. The CVE explicitly states the vulnerability was introduced in v6.11.1, and version 2.2.4 predates this by many major versions with a completely different implementation architecture."
    }
  ]
}