NIST National Vulnerability Database some records have the Vulnerability score (v3) value , but some records donot.Issue NIST National Vulnerability Database some records have the Vulnerability score (v3) value , but some records donot.Cause"NIST National Vulnerability Database" integration having the json urls with 1.0 version which is shipped out of the box. https://nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-modified.json.zipBut when customer with the integrations with 1.1 version which is the latest for the first time and changed the json url to 1.1 version. https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-recent.json.zipServiceNow is not updating the CVE entries if it has the last modified is same in the json payload and all the json payloads have same last modified fields for the same cves.ResolutionWork Around1. Run the below script to update the last modified of cves to a date before i.e 01-01-2015(As cvssV3 score is not supported before that by NVD):var cve = new GlideRecord("sn_vul_nvd_entry");cve.addEncodedQuery("scoreISNOTEMPTY^v3_base_scoreISEMPTY");cve.query();cve.setValue("last_modified","2015-01-01");cve.updateMultiple();Make sure that all the NVD Data feeds has 'Automatically update' flag to true and json urls with version '1.1'.Then run the integration "NIST National Vulnerability Database" .All the cvssv3 attributes would be populated on the CVE's.Related LinksGo to Vulnerability Response > Administration > NVD Auto Update Check : Automatically update is set to true and JSON URL end point https://instancename.service-now.com/sn_vul_nvd_repo_list.do?sysparm_query=active%3Dtrue&sysparm_view= Example ID : CVE-2019-19453 and CVE-2019-4589 . Here the column is Vulnerability score (v3) Vulnerability score (v3) : Table sn_vul_entry Field v3_base_score https://instance.service-now.com/sn_vul_nvd_entry_list.do?sysparm_query=idSTARTSWITHcve-2019-4589%5EORidSTARTSWITHCVE-2019-19453&sysparm_view=