{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:940a95c8-a528-56d6-b87d-8355a9652cd3",
  "version": 1,
  "metadata": {
    "tools": [
      {
        "name": "tuxcare-vex-generator",
        "version": "1.0.0"
      }
    ]
  },
  "components": [
    {
      "bom-ref": "pkg:npm/qs@2.2.4-tuxcare.1",
      "type": "library",
      "name": "qs",
      "version": "2.2.4-tuxcare.1",
      "purl": "pkg:npm/qs@2.2.4-tuxcare.1"
    }
  ],
  "vulnerabilities": [
    {
      "bom-ref": "urn:uuid:00092755-e566-5d78-8f4b-562627337b6b",
      "id": "CVE-2015-9251",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2015-9251 is fixed in version 2.2.4-tuxcare.1 of qs."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    },
    {
      "bom-ref": "urn:uuid:8b2b52da-ed59-5929-90cd-81724a7a4b1c",
      "id": "CVE-2017-1000048",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2017-1000048 is fixed in version 2.2.4-tuxcare.1 of qs."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    },
    {
      "bom-ref": "urn:uuid:5f5bcace-4c7b-5ae5-8e72-e671c89225d8",
      "id": "CVE-2019-11358",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2019-11358 is fixed in version 2.2.4-tuxcare.1 of qs."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    },
    {
      "bom-ref": "urn:uuid:72ed3a00-4fe3-5f58-9dde-8ad5c574d76a",
      "id": "CVE-2020-11022",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2020-11022 is fixed in version 2.2.4-tuxcare.1 of qs."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    },
    {
      "bom-ref": "urn:uuid:772ce304-95c0-59e1-b4bd-3a680b33e952",
      "id": "CVE-2020-11023",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2020-11023 is fixed in version 2.2.4-tuxcare.1 of qs."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    },
    {
      "bom-ref": "urn:uuid:95b5ef97-7165-557f-a2a3-4ba6b6459e41",
      "id": "CVE-2022-24999",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2022-24999 affects version 2.2.4-tuxcare.1 of qs."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    },
    {
      "bom-ref": "urn:uuid:00a3afa4-9578-5d5e-8614-e8e0c85594d3",
      "id": "CVE-2025-15284",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2025-15284 affects version 2.2.4-tuxcare.1 of qs."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    },
    {
      "bom-ref": "urn:uuid:2e57373c-64bd-5da9-92e5-d91dbdcb1bc8",
      "id": "CVE-2026-2391",
      "analysis": {
        "state": "not_affected",
        "detail": "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."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    },
    {
      "bom-ref": "urn:uuid:33ff3f43-051e-52f6-9ef9-f8467e208bca",
      "id": "CVE-2026-8723",
      "analysis": {
        "state": "not_affected",
        "detail": "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."
      },
      "affects": [
        {
          "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
        }
      ]
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/qs@2.2.4-tuxcare.1"
    }
  ]
}