{
  "@id": "urn:uuid:ca76b659-0c4f-407b-a5ef-96af788594b8",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 7,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-10-16T15:11:00.074533+00:00",
  "statements": [
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-16T15:11:00.074533+00:00",
      "status_notes": "Vulnerability CVE-2023-49293 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2023-49293"
      },
      "action_statement": "Vulnerability CVE-2023-49293 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.4."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-16T15:11:00.074533+00:00",
      "status_notes": "Vulnerability CVE-2024-23331 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2024-23331"
      },
      "action_statement": "Vulnerability CVE-2024-23331 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.4."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-16T15:11:00.074533+00:00",
      "status_notes": "Vulnerability CVE-2024-31207 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2024-31207"
      },
      "action_statement": "Vulnerability CVE-2024-31207 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.4."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-30T21:32:38.446662+00:00",
      "status_notes": "Vulnerability CVE-2024-45811 is fixed in version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2024-45811"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-16T15:11:00.074533+00:00",
      "status_notes": "Vulnerability CVE-2024-45812 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2024-45812"
      },
      "action_statement": "Vulnerability CVE-2024-45812 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.4."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-12T12:26:00.050264+00:00",
      "status_notes": "Vulnerability CVE-2024-52011 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2024-52011"
      },
      "action_statement": "Vulnerability CVE-2024-52011 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.2."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-15T12:13:41.094671+00:00",
      "status_notes": "Vulnerability CVE-2025-24010 affects version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2025-24010"
      },
      "action_statement": "Vulnerability CVE-2025-24010 affects version 4.5.0-tuxcare.1 of vite."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-30T21:32:38.446662+00:00",
      "status_notes": "Vulnerability CVE-2025-30208 is fixed in version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2025-30208"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-30T21:32:38.446662+00:00",
      "status_notes": "Vulnerability CVE-2025-31125 is fixed in version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2025-31125"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-15T12:13:41.094671+00:00",
      "status_notes": "Vulnerability CVE-2025-31486 affects version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2025-31486"
      },
      "action_statement": "Vulnerability CVE-2025-31486 affects version 4.5.0-tuxcare.1 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-15T12:13:41.094671+00:00",
      "status_notes": "Vulnerability CVE-2025-32395 affects version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2025-32395"
      },
      "action_statement": "Vulnerability CVE-2025-32395 affects version 4.5.0-tuxcare.1 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-15T12:13:41.094671+00:00",
      "status_notes": "Vulnerability CVE-2025-46565 affects version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2025-46565"
      },
      "action_statement": "Vulnerability CVE-2025-46565 affects version 4.5.0-tuxcare.1 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-15T12:13:41.094671+00:00",
      "status_notes": "Vulnerability CVE-2025-58751 affects version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2025-58751"
      },
      "action_statement": "Vulnerability CVE-2025-58751 affects version 4.5.0-tuxcare.1 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-15T12:13:41.094671+00:00",
      "status_notes": "Vulnerability CVE-2025-58752 affects version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2025-58752"
      },
      "action_statement": "Vulnerability CVE-2025-58752 affects version 4.5.0-tuxcare.1 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-12T12:26:00.050264+00:00",
      "status_notes": "Vulnerability CVE-2025-62522 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2025-62522"
      },
      "action_statement": "Vulnerability CVE-2025-62522 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.2."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-15T12:13:41.094671+00:00",
      "status_notes": "Vulnerability CVE-2026-39365 affects version 4.5.0-tuxcare.1 of vite.",
      "vulnerability": {
        "name": "CVE-2026-39365"
      },
      "action_statement": "Vulnerability CVE-2026-39365 affects version 4.5.0-tuxcare.1 of vite."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-12T12:26:00.050264+00:00",
      "status_notes": "Vulnerability CVE-2026-53571 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2026-53571"
      },
      "action_statement": "Vulnerability CVE-2026-53571 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.2."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:npm/vite@4.5.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/vite@4.5.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-12T19:34:00.110067+00:00",
      "status_notes": "Vulnerability CVE-2026-53632 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.3.",
      "vulnerability": {
        "name": "CVE-2026-53632"
      },
      "action_statement": "Vulnerability CVE-2026-53632 affects version 4.5.0-tuxcare.1 of vite, and is fixed in 4.5.0-tuxcare.3."
    }
  ]
}