{
  "@id": "urn:uuid:b7a4e262-b369-48a5-8cec-662a54e5507f",
  "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@5.2.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@5.2.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2017-1000048 is fixed in version 5.2.1-tuxcare.1 of qs.",
      "vulnerability": {
        "name": "CVE-2017-1000048"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/qs@5.2.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@5.2.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2022-24999 affects version 5.2.1-tuxcare.1 of qs, and is fixed in 5.2.1-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2022-24999"
      },
      "action_statement": "Vulnerability CVE-2022-24999 affects version 5.2.1-tuxcare.1 of qs, and is fixed in 5.2.1-tuxcare.2."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/qs@5.2.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@5.2.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-15284 is fixed in version 5.2.1-tuxcare.1 of qs.",
      "vulnerability": {
        "name": "CVE-2025-15284"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@5.2.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@5.2.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-2391 does not affect version 5.2.1-tuxcare.1 of qs. not_affected \u2014 The target repository (qs v5.2.1) is not affected by CVE-2026-2391. This vulnerability requires the `comma: true` option to enable parsing of comma-separated values into arrays, bypassing the `arrayLimit` enforcement. The `comma` option was introduced in qs v6.7.0 (commit b84acba, September 2018), which is well after v5.2.1. Since the feature does not exist in this version, the vulnerability ca...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-2391"
      },
      "impact_statement": "not_affected \u2014 The target repository (qs v5.2.1) is not affected by CVE-2026-2391. This vulnerability requires the `comma: true` option to enable parsing of comma-separated values into arrays, bypassing the `arrayLimit` enforcement. The `comma` option was introduced in qs v6.7.0 (commit b84acba, September 2018), which is well after v5.2.1. Since the feature does not exist in this version, the vulnerability ca..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/qs@5.2.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@5.2.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-82417 affects version 5.2.1-tuxcare.1 of qs, and is fixed in 5.2.1-tuxcare.3.",
      "vulnerability": {
        "name": "CVE-2026-82417"
      },
      "action_statement": "Vulnerability CVE-2026-82417 affects version 5.2.1-tuxcare.1 of qs, and is fixed in 5.2.1-tuxcare.3."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@5.2.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@5.2.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-82562 does not affect version 5.2.1-tuxcare.1 of qs. not_affected \u2014 The target qs version 5.2.1 is NOT affected by CVE-2026-82562. The vulnerability requires the `comma: true` option to enable comma-separated value parsing within individual query parameters (e.g., `a[]=1,2,3,4` parsed as four elements). This feature does not exist in version 5.2.1 - it was introduced in a later version. In 5.2.1, comma-separated values are treated as literal strings, not split ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-82562"
      },
      "impact_statement": "not_affected \u2014 The target qs version 5.2.1 is NOT affected by CVE-2026-82562. The vulnerability requires the `comma: true` option to enable comma-separated value parsing within individual query parameters (e.g., `a[]=1,2,3,4` parsed as four elements). This feature does not exist in version 5.2.1 - it was introduced in a later version. In 5.2.1, comma-separated values are treated as literal strings, not split ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/qs@5.2.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/qs@5.2.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-8723 does not affect version 5.2.1-tuxcare.1 of qs. not_affected \u2014 Version 5.2.1 is not affected by CVE-2026-8723. The vulnerability was introduced in commit 4c4b23d and first released in v6.11.1. Version 5.2.1 predates this vulnerable code by multiple major versions and lacks the arrayFormat='comma' option entirely. The existing code architecture safely handles null/undefined array elements through guards in the stringify function that prevent raw null/undefi...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-8723"
      },
      "impact_statement": "not_affected \u2014 Version 5.2.1 is not affected by CVE-2026-8723. The vulnerability was introduced in commit 4c4b23d and first released in v6.11.1. Version 5.2.1 predates this vulnerable code by multiple major versions and lacks the arrayFormat='comma' option entirely. The existing code architecture safely handles null/undefined array elements through guards in the stringify function that prevent raw null/undefi..."
    }
  ]
}