{
  "@id": "urn:uuid:80ec3af2-c16b-4e99-ba5f-69a8a4109e85",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-09-24T09:31:26.931840+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/formidable@2.1.2-tuxcare.5",
          "identifiers": {
            "purl": "pkg:npm/formidable@2.1.2-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-46653 does not affect version 2.1.2-tuxcare.5 of formidable. already_fixed \u2014 The target repository (formidable v2.1.2-tuxcare.5) already contains the security fix for CVE-2025-46653. Despite the version number being lower than 2.1.3, TuxCare has backported the upstream security patches (commits 022c2c5 and 37a3e89) that replace the non-cryptographically-secure hexoid library with @paralleldrive/cuid2 for filename generation. The fix is present and active in the current ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-46653"
      },
      "impact_statement": "already_fixed \u2014 The target repository (formidable v2.1.2-tuxcare.5) already contains the security fix for CVE-2025-46653. Despite the version number being lower than 2.1.3, TuxCare has backported the upstream security patches (commits 022c2c5 and 37a3e89) that replace the non-cryptographically-secure hexoid library with @paralleldrive/cuid2 for filename generation. The fix is present and active in the current ..."
    }
  ]
}