{
  "@id": "urn:uuid:012f0fe7-931a-4942-b2dc-8411d4847158",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 5,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T16:13:21.371966+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40vitest/ui@3.2.7",
          "identifiers": {
            "purl": "pkg:npm/%40vitest/ui@3.2.7"
          }
        }
      ],
      "timestamp": "2026-11-04T02:58:17.548486+00:00",
      "status_notes": "Vulnerability CVE-2026-112948 does not affect version 3.2.7 of @vitest/ui. not_affected \u2014 The target repository (vitest 3.2.7-tuxcare.2) is NOT AFFECTED by CVE-2026-112948. This vulnerability was introduced in Vitest 5 when the API token feature was added. Version 3.2.7 does not have the API token functionality, does not manipulate server.fs.deny, and relies entirely on Vite's default file-access protections which are properly applied. The vulnerability pattern described in the CVE\u2014...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-112948"
      },
      "impact_statement": "not_affected \u2014 The target repository (vitest 3.2.7-tuxcare.2) is NOT AFFECTED by CVE-2026-112948. This vulnerability was introduced in Vitest 5 when the API token feature was added. Version 3.2.7 does not have the API token functionality, does not manipulate server.fs.deny, and relies entirely on Vite's default file-access protections which are properly applied. The vulnerability pattern described in the CVE\u2014..."
    }
  ]
}
