{"id":"EUVD-2022-7013","revision":null,"records":[{"revision":"0f2d9ce0baf14a38b657d4a9ddb04ce3","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2022-3358","aliases":[],"title":"Using a Custom Cipher with NID_undef may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","state":0,"publishedAt":"2022-10-11T15:00:14.123+00:00","modifiedAt":"2024-09-16T16:33:30.64+00:00","affected":[{"ecosystem":"Vendor product","name":"OpenSSL","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"OpenSSL\",\n                    \"product\": \"OpenSSL\",\n                    \"versions\": [\n                        {\n                            \"version\": \"Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5)\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[],"references":["https://www.openssl.org/news/secadv/20221011.txt","https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=5485c56679d7c49b96e8fc8ca708b0b7e7c03c4b","https://security.netapp.com/advisory/ntap-20221028-0014/","https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023","https://security.gentoo.org/glsa/202402-08"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2022-3358","license":"CVE Program Terms of Use","key":"cve-program:CVE-2022-3358","identifiers":["CVE-2022-3358"]},"retained":false,"historicalAffected":[]},{"revision":"cc64b009f7cd474fb3ea970047bb9ec1","observedAt":"2026-11-18T03:29:42.244+00:00","statement":{"source":"euvd","id":"EUVD-2022-7013","aliases":["CVE-2022-3358","GHSA-4f63-89w9-3jjv"],"title":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechan…","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[],"references":["https://www.openssl.org/news/secadv/20221011.txt","https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=5485c56679d7c49b96e8fc8ca708b0b7e7c03c4b","https://security.netapp.com/advisory/ntap-20221028-0014/","https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023","https://security.gentoo.org/glsa/202402-08"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2022-7013","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Oct 11, 2022, 3:00:14 PM","dateUpdated":"Sep 16, 2024, 4:33:30 PM"},"relatedAdvisories":[{"id":"SUSE-SU-2022:3843-1","title":"Security update for openssl-3","vulnerabilityIds":["CVE-2022-3358","CVE-2022-3602","CVE-2022-3786"]},{"id":"RHSA-2023:2523","title":"Red Hat Security Advisory: openssl security and bug fix update","vulnerabilityIds":["CVE-2022-3358"]},{"id":"WID-SEC-W-2022-1690","title":"OpenSSL: Schwachstelle ermöglicht Offenlegung von Informationen","vulnerabilityIds":["CVE-2022-3358"]},{"id":"openSUSE-SU-2024:12475-1","title":"libopenssl-3-devel-3.0.7-1.1 on GA media","vulnerabilityIds":["CVE-2022-3358","CVE-2022-3602","CVE-2022-3786"]},{"id":"WID-SEC-W-2023-1542","title":"Red Hat OpenShift: Mehrere Schwachstellen","vulnerabilityIds":["CVE-2015-20107","CVE-2018-25032","CVE-2020-10735","CVE-2020-16250","CVE-2020-16251","CVE-2020-17049","CVE-2021-28861","CVE-2021-3765","CVE-2021-3807","CVE-2021-4231","CVE-2021-4235","CVE-2021-4238","CVE-2021-43519","CVE-2021-43998","CVE-2021-44531","CVE-2021-44532","CVE-2021-44533","CVE-2021-44964","CVE-2021-46828","CVE-2021-46848","CVE-2022-0670","CVE-2022-1271","CVE-2022-1304","CVE-2022-1348","CVE-2022-1586","CVE-2022-1587","CVE-2022-21824","CVE-2022-2309","CVE-2022-23540","CVE-2022-23541","CVE-2022-24903","CVE-2022-2509","CVE-2022-26280","CVE-2022-27664","CVE-2022-2795","CVE-2022-2879","CVE-2022-2880","CVE-2022-28805","CVE-2022-29154","CVE-2022-30635","CVE-2022-3094","CVE-2022-31129","CVE-2022-32189","CVE-2022-32190","CVE-2022-33099","CVE-2022-3358","CVE-2022-34903","CVE-2022-3515","CVE-2022-3517","CVE-2022-35737","CVE-2022-36227","CVE-2022-3715","CVE-2022-3736","CVE-2022-37434","CVE-2022-38149","CVE-2022-3821","CVE-2022-38900","CVE-2022-3924","CVE-2022-40023","CVE-2022-40303","CVE-2022-40304","CVE-2022-40897","CVE-2022-41316","CVE-2022-41715","CVE-2022-41717","CVE-2022-41723","CVE-2022-41724","CVE-2022-41725","CVE-2022-42010","CVE-2022-42011","CVE-2022-42012","CVE-2022-42898","CVE-2022-42919","CVE-2022-43680","CVE-2022-4415","CVE-2022-45061","CVE-2022-45873","CVE-2022-46175","CVE-2022-47024","CVE-2022-47629","CVE-2022-48303","CVE-2022-48337","CVE-2022-48338","CVE-2022-48339","CVE-2023-0361","CVE-2023-0620","CVE-2023-0665","CVE-2023-22809","CVE-2023-24329","CVE-2023-2491","CVE-2023-24999","CVE-2023-25000","CVE-2023-25136"]}],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2022-7013","identifiers":["EUVD-2022-7013","CVE-2022-3358","GHSA-4f63-89w9-3jjv"]},"retained":false,"historicalAffected":[]},{"revision":"5a618d33553542ffb27034256a8a3da3","observedAt":"2026-10-24T20:17:30.291+00:00","statement":{"source":"nvd","id":"CVE-2022-3358","aliases":[],"title":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechan…","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","state":0,"publishedAt":"2022-10-11T15:15:10.233+00:00","modifiedAt":"2026-06-17T04:59:22.627+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · nvd@nist.gov · Primary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","score":7.5,"severity":"HIGH"}],"references":["https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=5485c56679d7c49b96e8fc8ca708b0b7e7c03c4b","https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023","https://security.gentoo.org/glsa/202402-08","https://security.netapp.com/advisory/ntap-20221028-0014/","https://www.openssl.org/news/secadv/20221011.txt"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2022-3358","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Modified","weaknesses":["CWE-476"],"productCriteria":["cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*"],"sourceDates":{"published":"2022-10-11T15:15:10.233","lastModified":"2026-06-17T04:59:22.627"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2022-3358","identifiers":["CVE-2022-3358"]},"retained":false,"historicalAffected":[]},{"revision":"2092b94632b54397ba3e91915b5fcc5a","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-4f63-89w9-3jjv","aliases":["CVE-2022-3358","RUSTSEC-2022-0059"],"title":"Using a Custom Cipher with `NID_undef` may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","state":0,"publishedAt":"2022-10-11T19:00:29+00:00","modifiedAt":"2026-09-10T03:49:46.182272+00:00","affected":[{"ecosystem":"crates.io","name":"openssl-src","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"300.0.0"},{"kind":"fixed","version":"300.0.10"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://nvd.nist.gov/vuln/detail/CVE-2022-3358","https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=5485c56679d7c49b96e8fc8ca708b0b7e7c03c4b","https://github.com/alexcrichton/openssl-src-rs","https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023","https://rustsec.org/advisories/RUSTSEC-2022-0059.html","https://security.gentoo.org/glsa/202402-08","https://security.netapp.com/advisory/ntap-20221028-0014","https://www.openssl.org/news/secadv/20221011.txt"],"sourceUrl":"https://github.com/advisories/GHSA-4f63-89w9-3jjv","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-4f63-89w9-3jjv","identifiers":["GHSA-4f63-89w9-3jjv","CVE-2022-3358","RUSTSEC-2022-0059"]},"retained":false,"historicalAffected":[]},{"revision":"fb878389336f400aaf3ee9243970230e","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"RUSTSEC-2022-0059","aliases":["CVE-2022-3358","GHSA-4f63-89w9-3jjv"],"title":"Using a Custom Cipher with `NID_undef` may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy `EVP_CIPHER_meth_new()`\nfunction and associated function calls. This function was deprecated in OpenSSL\n3.0 and application authors are instead encouraged to use the new provider\nmechanism in order to implement custom ciphers.\n\nOpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed\nto the `EVP_EncryptInit_ex2()`, `EVP_DecryptInit_ex2()` and `EVP_CipherInit_ex2()`\nfunctions (as well as other similarly named encryption and decryption\ninitialisation functions). Instead of using the custom cipher directly it\nincorrectly tries to fetch an equivalent cipher from the available providers.\nAn equivalent cipher is found based on the NID passed to `EVP_CIPHER_meth_new()`.\nThis NID is supposed to represent the unique NID for a given cipher. However it\nis possible for an application to incorrectly pass `NID_undef` as this value in\nthe call to `EVP_CIPHER_meth_new()`. When `NID_undef` is used in this way the\nOpenSSL encryption/decryption initialisation function will match the NULL cipher\nas being equivalent and will fetch this from the available providers. This will\nsucceed if the default provider has been loaded (or if a third party provider\nhas been loaded that offers this cipher). Using the NULL cipher means that the\nplaintext is emitted as the ciphertext.\n\nApplications are only affected by this issue if they call `EVP_CIPHER_meth_new()`\nusing `NID_undef` and subsequently use it in a call to an encryption/decryption\ninitialisation function. Applications that only use SSL/TLS are not impacted by\nthis issue.","state":0,"publishedAt":"2022-10-11T12:00:00+00:00","modifiedAt":"2023-11-08T04:09:40.031051+00:00","affected":[{"ecosystem":"crates.io","name":"openssl-src","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"300.0.0"},{"kind":"fixed","version":"300.0.10"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://crates.io/crates/openssl-src","https://rustsec.org/advisories/RUSTSEC-2022-0059.html","https://www.openssl.org/news/secadv/20221011.txt"],"sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2022-0059","license":"OSV · upstream source license applies","key":"osv:RUSTSEC-2022-0059","identifiers":["RUSTSEC-2022-0059","CVE-2022-3358","GHSA-4f63-89w9-3jjv"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-19T05:22:48.4383343+00:00","complete":true,"records":1786,"lastAttemptAt":"2026-11-19T05:22:48.4383343+00:00","lastSuccessAt":"2026-11-19T05:22:48.5819004+00:00","error":null,"lastVerifiedAt":"2026-11-19T05:22:48.581904+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-e55c589538e0700b45c7d6d41fe1447a79199283262c371c864535c791a040b9-a3c5d1f50b99987b637138fdc7cd9e1e0d772b1c81dbbff4bcc8be865c192a98","complete":true,"records":428232,"lastAttemptAt":"2026-11-19T05:22:47.9486287+00:00","lastSuccessAt":"2026-11-19T05:22:47.9265788+00:00","error":null,"lastVerifiedAt":"2026-11-19T05:22:47.9486287+00:00","snapshotPublishedAt":"2026-11-19T04:33:18+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-7c1103063ba0426d8e585240e558964c","complete":false,"records":13861,"lastAttemptAt":"2026-11-19T05:32:28.4240909+00:00","lastSuccessAt":"2026-11-19T05:32:27.403+00:00","error":"218 identifier lookups failed; latest failures include AccessDenied (HTTP 403). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-19T05:32:27.403+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13568,"expectedIdentifiers":13908,"failedIdentifiers":218},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-19T05:22:48.4383343+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-19T05:22:48.4383343+00:00","lastSuccessAt":"2026-11-19T05:22:48.5827402+00:00","error":null,"lastVerifiedAt":"2026-11-19T05:22:48.5827403+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-84b4b212d7ef41cb9ec24b71e9d8e5d8","complete":true,"records":13873,"lastAttemptAt":"2026-11-19T05:22:49.1394496+00:00","lastSuccessAt":"2026-11-19T04:24:39.391+00:00","error":null,"lastVerifiedAt":"2026-11-19T04:24:39.391+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13908,"expectedIdentifiers":13908,"failedIdentifiers":0},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-76574c95b6792d47ba90af64983ed5843633f14426346d676016e94a5f383202","complete":true,"records":9963,"lastAttemptAt":"2026-11-19T05:22:48.2819697+00:00","lastSuccessAt":"2026-11-19T01:24:31.4213722+00:00","error":null,"lastVerifiedAt":"2026-11-19T05:22:48.2819697+00:00","snapshotPublishedAt":"2026-11-19T01:03:15+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-19T05:22:48.0028407+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-19T05:22:48.0028407+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-c0d9c71c6fa06d617f979e7bec0d97aca70ca5aea1558184002f8e44516f2fac","complete":true,"records":3177,"lastAttemptAt":"2026-11-19T05:22:48.391557+00:00","lastSuccessAt":"2026-11-18T21:25:09.5127964+00:00","error":null,"lastVerifiedAt":"2026-11-19T05:22:48.391557+00:00","snapshotPublishedAt":"2026-11-18T21:18:06+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-2556fa291ec863b7fd77332e55dcff5569878e06b48ea32c182e52878cdd1ce8","complete":true,"records":232702,"lastAttemptAt":"2026-11-19T05:22:48.1723185+00:00","lastSuccessAt":"2026-11-19T04:24:35.8955272+00:00","error":null,"lastVerifiedAt":"2026-11-19T05:22:48.1723185+00:00","snapshotPublishedAt":"2026-11-19T03:33:12+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}