Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY9 SECURITY RECORDS

ServiceNow

Now Platform

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2025-3648 8 Jul 2025 Aspen No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-0337 6 Mar 2025 < Washington DC Patch 9; < Xanadu Patch 4; < Yokohama No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-5890 2 Dec 2024 < Utah Patch 8 Hot Fix 1; < Vancouver Patch 10; < Vancouver Patch 9; < Washington DC Early Access No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8924 29 Oct 2024 < Utah Patch 10b Hot Fix 3; < Vancouver Patch 8 Hot Fix 5; < Vancouver Patch 9 Hot Fix 3b; < Vancouver Patch 10 Hot Fix 2; < Washington DC Patch 4 Hot Fix 2b; < Washington DC Patch 5 Hot Fix 6; < Washington DC Patch 6 Hot Fix 1; < Washington DC Patch 7 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-8923 29 Oct 2024 < Vancouver Patch 9 Hot Fix 2a; < Vancouver Patch 10; < Washington DC Patch 4 Hot Fix 1a; < Washington DC Patch 5; < Xanadu GA Release No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-5178 10 Jul 2024 < Utah Patch 10 Hot Fix 3; < Utah Patch 10a Hot Fix 2; < Utah Patch 10b Hot Fix 1; < Vancouver Patch 6 Hot Fix 2; < Vancouver Patch 7 Hot Fix 3b; < Vancouver Patch 8 Hot Fix 4; < Vancouver Patch 9 Hot Fix 1; < Vancouver Patch 10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-43684 13 Jun 2023 Quebec < Patch 10 Hot Fix 8b; Rome < Patch 10 Hot Fix 1; San Diego < Patch 7; Tokyo < Tokyo Patch 1; Utah < Utah General Availability (GA) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-46389 17 Apr 2023 Quebec < Patch 10 Hotfix 11b; Rome < Patch 10 Hotfix 3b; San Diego < Patch 9; Tokyo < Patch 4; Utah < GA No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-39048 10 Apr 2023 Tokyo < Patch 1a; San Diego < Patch 7b; Rome < Patch 10 Hotfix 2b; Quebec < Patch 10 Hotfix 10b No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.