{
  "@id": "urn:uuid:55f826b6-7e9d-4ccc-9e75-7b6799964e8c",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 6,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-14T01:20:14.027368+00:00",
  "statements": [
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-04T04:52:00.041416+00:00",
      "status_notes": "Vulnerability CVE-2022-35204 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2022-35204"
      },
      "action_statement": "Vulnerability CVE-2022-35204 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-04T04:52:00.041416+00:00",
      "status_notes": "Vulnerability CVE-2023-34092 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2023-34092"
      },
      "action_statement": "Vulnerability CVE-2023-34092 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2023-49293 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2023-49293"
      },
      "action_statement": "Vulnerability CVE-2023-49293 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2024-23331 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2024-23331"
      },
      "action_statement": "Vulnerability CVE-2024-23331 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2024-31207 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2024-31207"
      },
      "action_statement": "Vulnerability CVE-2024-31207 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2024-45811 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2024-45811"
      },
      "action_statement": "Vulnerability CVE-2024-45811 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2024-45812 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2024-45812"
      },
      "action_statement": "Vulnerability CVE-2024-45812 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2024-52011 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2024-52011"
      },
      "action_statement": "Vulnerability CVE-2024-52011 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2025-24010 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2025-24010"
      },
      "action_statement": "Vulnerability CVE-2025-24010 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2025-30208 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2025-30208"
      },
      "action_statement": "Vulnerability CVE-2025-30208 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2025-31125 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2025-31125"
      },
      "action_statement": "Vulnerability CVE-2025-31125 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2025-31486 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2025-31486"
      },
      "action_statement": "Vulnerability CVE-2025-31486 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2025-32395 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2025-32395"
      },
      "action_statement": "Vulnerability CVE-2025-32395 affects version 4.4.6 of vite."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-14T01:19:51.646033+00:00",
      "status_notes": "Vulnerability CVE-2025-46565 does not affect version 4.4.6 of vite. not_affected \u2014 Vite 4.4.6 is not exposed to the `/.env/.` deny bypass as far as I could verify. The `/.` request is normalized to `/.env/` by the WHATWG URL parser, and the deny matcher (picomatch 2.x with matchBase) still matches that form. The static middleware therefore rejects the request before sirv serves it. I did not run a live dev server; this rests on code reading plus a test of the picomatch matche...",
      "vulnerability": {
        "name": "CVE-2025-46565"
      },
      "impact_statement": "not_affected \u2014 Vite 4.4.6 is not exposed to the `/.env/.` deny bypass as far as I could verify. The `/.` request is normalized to `/.env/` by the WHATWG URL parser, and the deny matcher (picomatch 2.x with matchBase) still matches that form. The static middleware therefore rejects the request before sirv serves it. I did not run a live dev server; this rests on code reading plus a test of the picomatch matche..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2025-58751 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2025-58751"
      },
      "action_statement": "Vulnerability CVE-2025-58751 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2025-58752 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2025-58752"
      },
      "action_statement": "Vulnerability CVE-2025-58752 affects version 4.4.6 of vite."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-14T01:20:14.027368+00:00",
      "status_notes": "Vulnerability CVE-2025-62522 does not affect version 4.4.6 of vite. not_affected \u2014 Vite 4.4.6 is not affected by the default-configuration bypass in CVE-2025-62522. The deny glob is built with picomatch `matchBase: true`, which tests each pattern against `path.basename(file)`. `path.basename` strips the trailing separator that a request ending in `\\` turns into. The default patterns (`.env`, `.env.*`, `*.{crt,pem}`) therefore still match `.env/`. The upstream bypass depends o...",
      "vulnerability": {
        "name": "CVE-2025-62522"
      },
      "impact_statement": "not_affected \u2014 Vite 4.4.6 is not affected by the default-configuration bypass in CVE-2025-62522. The deny glob is built with picomatch `matchBase: true`, which tests each pattern against `path.basename(file)`. `path.basename` strips the trailing separator that a request ending in `\\` turns into. The default patterns (`.env`, `.env.*`, `*.{crt,pem}`) therefore still match `.env/`. The upstream bypass depends o..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-112942 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-112942"
      },
      "action_statement": "Vulnerability CVE-2026-112942 affects version 4.4.6 of vite."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-14T01:19:00.090898+00:00",
      "status_notes": "Vulnerability CVE-2026-112943 does not affect version 4.4.6 of vite. not_affected \u2014 The target is Vite 4.4.6, not launch-editor. The vulnerable cmd.exe argument-escaping code (missing '%' escape) is not in this repository. Vite only declares launch-editor-middleware ^2.6.0 as a dependency (locked at launch-editor 2.6.0) and mounts it at /__open-in-editor. No source for the flawed function is vendored in the tree. The flaw lives entirely in the external dependency, so the repo'...",
      "vulnerability": {
        "name": "CVE-2026-112943"
      },
      "impact_statement": "not_affected \u2014 The target is Vite 4.4.6, not launch-editor. The vulnerable cmd.exe argument-escaping code (missing '%' escape) is not in this repository. Vite only declares launch-editor-middleware ^2.6.0 as a dependency (locked at launch-editor 2.6.0) and mounts it at /__open-in-editor. No source for the flawed function is vendored in the tree. The flaw lives entirely in the external dependency, so the repo'..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-112944 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-112944"
      },
      "action_statement": "Vulnerability CVE-2026-112944 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-112945 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-112945"
      },
      "action_statement": "Vulnerability CVE-2026-112945 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-112946 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-112946"
      },
      "action_statement": "Vulnerability CVE-2026-112946 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-112947 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-112947"
      },
      "action_statement": "Vulnerability CVE-2026-112947 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-118662 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-118662"
      },
      "action_statement": "Vulnerability CVE-2026-118662 affects version 4.4.6 of vite."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-14T01:18:00.089817+00:00",
      "status_notes": "Vulnerability CVE-2026-39363 does not affect version 4.4.6 of vite. not_affected \u2014 Vite 4.4.6 does not have the vulnerable `fetchModule` / `vite:invoke` WebSocket RPC path. The only server-side WebSocket custom-event listener in core is `vite:invalidate`. It does only an in-memory module-graph lookup and never reads files or returns file contents. No WebSocket-reachable chain to arbitrary file disclosure exists, so the CVE does not apply to this version. No fix commit is need...",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2026-39363"
      },
      "impact_statement": "not_affected \u2014 Vite 4.4.6 does not have the vulnerable `fetchModule` / `vite:invoke` WebSocket RPC path. The only server-side WebSocket custom-event listener in core is `vite:invalidate`. It does only an in-memory module-graph lookup and never reads files or returns file contents. No WebSocket-reachable chain to arbitrary file disclosure exists, so the CVE does not apply to this version. No fix commit is need..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-39364 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-39364"
      },
      "action_statement": "Vulnerability CVE-2026-39364 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-39365 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-39365"
      },
      "action_statement": "Vulnerability CVE-2026-39365 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-53571 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-53571"
      },
      "action_statement": "Vulnerability CVE-2026-53571 affects version 4.4.6 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.4.6",
          "identifiers": {
            "purl": "pkg:npm/vite@4.4.6"
          }
        }
      ],
      "timestamp": "2026-11-03T17:39:04.334122+00:00",
      "status_notes": "Vulnerability CVE-2026-53632 affects version 4.4.6 of vite.",
      "vulnerability": {
        "name": "CVE-2026-53632"
      },
      "action_statement": "Vulnerability CVE-2026-53632 affects version 4.4.6 of vite."
    }
  ]
}