{
  "@id": "urn:uuid:b93cbbc2-bd1a-4149-9195-ece77fdd6034",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 8,
  "@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/%40nuxt/vite-builder@3.2.0-tuxcare.7",
          "identifiers": {
            "purl": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-10-13T19:54:00.089433+00:00",
      "status_notes": "Vulnerability CVE-2022-25852 is a false positive for @nuxt/vite-builder 3.2.0-tuxcare.7. CVE-2022-25852 is a false positive for this repository. The CVE affects pg-native and libpq npm packages (PostgreSQL database client bindings), but this repository is the Nuxt.js web framework (version 3.2.0-tuxcare.4). Exhaustive containment search found no pg-native/libpq code in the repository - not as the project itself, not as a vendored/bundled copy, and not as a declared dependency. This is a wrong-project match.",
      "vulnerability": {
        "name": "CVE-2022-25852"
      },
      "impact_statement": "CVE-2022-25852 is a false positive for this repository. The CVE affects pg-native and libpq npm packages (PostgreSQL database client bindings), but this repository is the Nuxt.js web framework (version 3.2.0-tuxcare.4). Exhaustive containment search found no pg-native/libpq code in the repository - not as the project itself, not as a vendored/bundled copy, and not as a declared dependency. This is a wrong-project match."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7",
          "identifiers": {
            "purl": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-02T20:48:40.075758+00:00",
      "status_notes": "Vulnerability CVE-2025-24360 affects version 3.2.0-tuxcare.7 of @nuxt/vite-builder.",
      "vulnerability": {
        "name": "CVE-2025-24360"
      },
      "action_statement": "Vulnerability CVE-2025-24360 affects version 3.2.0-tuxcare.7 of @nuxt/vite-builder."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7",
          "identifiers": {
            "purl": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T01:00:02.558489+00:00",
      "status_notes": "Vulnerability CVE-2026-119198 does not affect version 3.2.0-tuxcare.7 of @nuxt/vite-builder. not_affected \u2014 Nuxt 3.2.0-tuxcare.11 is NOT AFFECTED by CVE-2026-119198. The vulnerability exists only in Nuxt 4.6.0-4.6.2 in the dev-errors.ts file, which handles `nuxt:dev:client-error` WebSocket events and reads files based on client-reported error messages. This entire error reporting infrastructure does not exist in Nuxt 3.x. The vulnerable code was introduced in commit 66d6797dde (Sept 2026) as part of ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-119198"
      },
      "impact_statement": "not_affected \u2014 Nuxt 3.2.0-tuxcare.11 is NOT AFFECTED by CVE-2026-119198. The vulnerability exists only in Nuxt 4.6.0-4.6.2 in the dev-errors.ts file, which handles `nuxt:dev:client-error` WebSocket events and reads files based on client-reported error messages. This entire error reporting infrastructure does not exist in Nuxt 3.x. The vulnerable code was introduced in commit 66d6797dde (Sept 2026) as part of ..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7",
          "identifiers": {
            "purl": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-10-30T23:06:48.799530+00:00",
      "status_notes": "Vulnerability CVE-2026-119199 affects version 3.2.0-tuxcare.7 of @nuxt/vite-builder.",
      "vulnerability": {
        "name": "CVE-2026-119199"
      },
      "action_statement": "Vulnerability CVE-2026-119199 affects version 3.2.0-tuxcare.7 of @nuxt/vite-builder."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7",
          "identifiers": {
            "purl": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T00:54:55.163264+00:00",
      "status_notes": "Vulnerability CVE-2026-119201 does not affect version 3.2.0-tuxcare.7 of @nuxt/vite-builder. not_affected \u2014 CVE-2026-119201 affects Nuxt.js versions that include the appSecret feature, which generates a development secret file at `.nuxt/app-secret` that can be exposed via Vite's `/@fs/` route. Version 3.2.0-tuxcare.11 is NOT affected because the appSecret feature does not exist in this version. The feature was introduced in commit ab9c83279 (September 2026), which is not an ancestor of this version's...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-119201"
      },
      "impact_statement": "not_affected \u2014 CVE-2026-119201 affects Nuxt.js versions that include the appSecret feature, which generates a development secret file at `.nuxt/app-secret` that can be exposed via Vite's `/@fs/` route. Version 3.2.0-tuxcare.11 is NOT affected because the appSecret feature does not exist in this version. The feature was introduced in commit ab9c83279 (September 2026), which is not an ancestor of this version's..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7",
          "identifiers": {
            "purl": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-10-13T19:54:00.089433+00:00",
      "status_notes": "Vulnerability GHSA-c9cv-mq2m-ppp3 does not affect version 3.2.0-tuxcare.7 of @nuxt/vite-builder. not_affected \u2014 Target repository Nuxt version 3.2.0 is NOT affected by GHSA-c9cv-mq2m-ppp3. All three vulnerability sinks described in the CVE (SSR open redirect via path-normalization, script execution via navigateTo open option, and protocol-relative bypass in reloadNuxtApp) require code features that were introduced AFTER version 3.2.0. The vulnerable encodeURL function with WHATWG URL parsing was added in...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "GHSA-c9cv-mq2m-ppp3"
      },
      "impact_statement": "not_affected \u2014 Target repository Nuxt version 3.2.0 is NOT affected by GHSA-c9cv-mq2m-ppp3. All three vulnerability sinks described in the CVE (SSR open redirect via path-normalization, script execution via navigateTo open option, and protocol-relative bypass in reloadNuxtApp) require code features that were introduced AFTER version 3.2.0. The vulnerable encodeURL function with WHATWG URL parsing was added in..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7",
          "identifiers": {
            "purl": "pkg:npm/%40nuxt/vite-builder@3.2.0-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-10-13T19:54:00.089433+00:00",
      "status_notes": "Vulnerability GHSA-m3q2-p4fw-w38m does not affect version 3.2.0-tuxcare.7 of @nuxt/vite-builder. not_affected \u2014 Version 3.2.0 is NOT affected by GHSA-m3q2-p4fw-w38m. The vulnerable innerHTML pattern was introduced in v3.16.0 (March 2025), two years after this version. The target uses noscript.children instead of the vulnerable noscript.innerHTML assignment.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "GHSA-m3q2-p4fw-w38m"
      },
      "impact_statement": "not_affected \u2014 Version 3.2.0 is NOT affected by GHSA-m3q2-p4fw-w38m. The vulnerable innerHTML pattern was introduced in v3.16.0 (March 2025), two years after this version. The target uses noscript.children instead of the vulnerable noscript.innerHTML assignment."
    }
  ]
}