{"id":"CVE-2025-58058","revision":null,"records":[{"revision":"e12dd40d1024440e83cd8f9f3c16b368","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2025-58058","aliases":[],"title":"github.com/ulikunitz/xz leaks memory when decoding a corrupted multiple LZMA archives","description":"xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.","state":0,"publishedAt":"2025-08-28T21:54:05.561+00:00","modifiedAt":"2025-08-29T13:23:07.497+00:00","affected":[{"ecosystem":"Vendor product","name":"xz","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"ulikunitz\",\n                    \"product\": \"xz\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 0.5.14\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","score":5.3,"severity":"MEDIUM"}],"references":["https://github.com/ulikunitz/xz/security/advisories/GHSA-jc7w-c686-c4v9","https://github.com/ulikunitz/xz/commit/88ddf1d0d98d688db65de034f48960b2760d2ae2"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-58058","license":"CVE Program Terms of Use","key":"cve-program:CVE-2025-58058","identifiers":["CVE-2025-58058"]},"retained":false,"historicalAffected":[]},{"revision":"9a932c2853664ce3890f9139e53da039","observedAt":"2026-11-11T03:36:12.704+00:00","statement":{"source":"euvd","id":"EUVD-2025-26149","aliases":["CVE-2025-58058","GHSA-jc7w-c686-c4v9"],"title":"xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to …","description":"xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","score":5.3,"severity":null}],"references":["https://github.com/ulikunitz/xz/security/advisories/GHSA-jc7w-c686-c4v9","https://github.com/ulikunitz/xz/commit/88ddf1d0d98d688db65de034f48960b2760d2ae2"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-26149","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Aug 28, 2025, 9:54:05 PM","dateUpdated":"Aug 29, 2025, 1:23:07 PM"},"relatedAdvisories":[{"id":"SUSE-SU-2025:03448-1","title":"Security update for warewulf4","vulnerabilityIds":["CVE-2025-58058"]},{"id":"msrc_CVE-2025-58058","title":"github.com/ulikunitz/xz leaks memory when decoding a corrupted multiple LZMA archives","vulnerabilityIds":["CVE-2025-58058"]},{"id":"SUSE-SU-2026:0383-1","title":"Security update for rekor","vulnerabilityIds":["CVE-2025-29923","CVE-2025-58058"]},{"id":"openSUSE-SU-2025:15509-1","title":"sbctl-0.17-2.1 on GA media","vulnerabilityIds":["CVE-2025-58058"]},{"id":"RHSA-2026:26254","title":"Red Hat Security Advisory: Assisted Installer RHEL 9 components for Multicluster Engine for Kubernetes 2.8.8","vulnerabilityIds":["CVE-2025-58058","CVE-2026-39883"]},{"id":"openSUSE-SU-2026:21824-1","title":"Security update for containerized-data-importer1.65","vulnerabilityIds":["CVE-2025-22869","CVE-2025-22870","CVE-2025-22872","CVE-2025-47911","CVE-2025-47913","CVE-2025-47914","CVE-2025-58058","CVE-2025-58181","CVE-2025-58190","CVE-2026-25680","CVE-2026-25681","CVE-2026-27136","CVE-2026-33186","CVE-2026-33814","CVE-2026-34986","CVE-2026-35469","CVE-2026-39821","CVE-2026-39827","CVE-2026-39828","CVE-2026-39829","CVE-2026-39830","CVE-2026-39831","CVE-2026-39832","CVE-2026-39833","CVE-2026-39834","CVE-2026-39835","CVE-2026-41178","CVE-2026-42502","CVE-2026-42506","CVE-2026-42508","CVE-2026-46595","CVE-2026-46597","CVE-2026-46598","CVE-2026-56852","CVE-2026-56854","CVE-2026-56855","CVE-2026-78662","CVE-2026-84303","CVE-2026-84304"]},{"id":"SUSE-SU-2025:4121-1","title":"Security update for alloy","vulnerabilityIds":["CVE-2025-11065","CVE-2025-58058"]},{"id":"openSUSE-SU-2026:21151-1","title":"Security update for warewulf4","vulnerabilityIds":["CVE-2025-58058","CVE-2025-69725","CVE-2026-33814","CVE-2026-34986","CVE-2026-39821"]},{"id":"RHSA-2026:26257","title":"Red Hat Security Advisory: Assisted Installer RHEL 8 components for Multicluster Engine for Kubernetes 2.8.8","vulnerabilityIds":["CVE-2025-58058","CVE-2026-39883"]},{"id":"openSUSE-SU-2026:20798-1","title":"Security update for trivy","vulnerabilityIds":["CVE-2024-3817","CVE-2024-45337","CVE-2024-45338","CVE-2024-51744","CVE-2025-11065","CVE-2025-21613","CVE-2025-21614","CVE-2025-22868","CVE-2025-22869","CVE-2025-22872","CVE-2025-27144","CVE-2025-30204","CVE-2025-46569","CVE-2025-47291","CVE-2025-47911","CVE-2025-47913","CVE-2025-47914","CVE-2025-53547","CVE-2025-58058","CVE-2025-58181","CVE-2025-58190"]},{"id":"openSUSE-SU-2026:11305-1","title":"containerized-data-importer1.65-api-1.65.0-2.1 on GA media","vulnerabilityIds":["CVE-2025-22870","CVE-2025-22872","CVE-2025-58058","CVE-2025-58190","CVE-2026-27136","CVE-2026-33186","CVE-2026-34986","CVE-2026-35469","CVE-2026-39821","CVE-2026-39827","CVE-2026-39828","CVE-2026-39832","CVE-2026-42508"]},{"id":"openSUSE-SU-2026:20105-1","title":"Security update for sbctl","vulnerabilityIds":["CVE-2025-47911","CVE-2025-58058","CVE-2025-58190"]},{"id":"openSUSE-SU-2025-20073-1","title":"Security update for alloy","vulnerabilityIds":["CVE-2025-11065","CVE-2025-58058"]},{"id":"openSUSE-SU-2025:15722-1","title":"hauler-1.3.1-1.1 on GA media","vulnerabilityIds":["CVE-2025-11579","CVE-2025-47911","CVE-2025-58058"]},{"id":"openSUSE-SU-2025:20117-1","title":"Security update for trivy","vulnerabilityIds":["CVE-2024-3817","CVE-2024-45337","CVE-2024-45338","CVE-2024-51744","CVE-2025-11065","CVE-2025-21613","CVE-2025-21614","CVE-2025-22868","CVE-2025-22869","CVE-2025-22872","CVE-2025-27144","CVE-2025-30204","CVE-2025-46569","CVE-2025-47291","CVE-2025-53547","CVE-2025-58058"]},{"id":"openSUSE-SU-2025-20031-1","title":"Security update for warewulf4","vulnerabilityIds":["CVE-2025-58058"]},{"id":"openSUSE-SU-2025-20117-1","title":"Security update for trivy","vulnerabilityIds":["CVE-2024-3817","CVE-2024-45337","CVE-2024-45338","CVE-2024-51744","CVE-2025-11065","CVE-2025-21613","CVE-2025-21614","CVE-2025-22868","CVE-2025-22869","CVE-2025-22872","CVE-2025-27144","CVE-2025-30204","CVE-2025-46569","CVE-2025-47291","CVE-2025-53547","CVE-2025-58058"]},{"id":"openSUSE-SU-2025:20160-1","title":"Security update for hauler","vulnerabilityIds":["CVE-2024-0406","CVE-2024-45338","CVE-2025-11579","CVE-2025-22872","CVE-2025-46569","CVE-2025-47911","CVE-2025-58058","CVE-2025-58190"]},{"id":"openSUSE-SU-2025:20031-1","title":"Security update for warewulf4","vulnerabilityIds":["CVE-2025-58058"]},{"id":"openSUSE-SU-2026:11126-1","title":"velociraptor-0.7.0.4.git185.a5708584-2.1 on GA media","vulnerabilityIds":["CVE-2023-45288","CVE-2024-45339","CVE-2025-13465","CVE-2025-22868","CVE-2025-22869","CVE-2025-22870","CVE-2025-22872","CVE-2025-24358","CVE-2025-47911","CVE-2025-58058","CVE-2025-58181","CVE-2025-58190","CVE-2025-5889","CVE-2025-64718","CVE-2025-6545","CVE-2025-6547","CVE-2025-7783","CVE-2026-1229","CVE-2026-25128","CVE-2026-25680","CVE-2026-25681","CVE-2026-26278","CVE-2026-26996","CVE-2026-27136","CVE-2026-2739","CVE-2026-27606","CVE-2026-27904","CVE-2026-33036","CVE-2026-33186","CVE-2026-33487","CVE-2026-33814","CVE-2026-34986","CVE-2026-39821","CVE-2026-39827","CVE-2026-39828","CVE-2026-39829","CVE-2026-39830","CVE-2026-39831","CVE-2026-39832","CVE-2026-39833","CVE-2026-39834","CVE-2026-39835","CVE-2026-42039","CVE-2026-42502","CVE-2026-42506","CVE-2026-42508","CVE-2026-46595","CVE-2026-46597","CVE-2026-46598"]},{"id":"openSUSE-SU-2025:15631-1","title":"alloy-1.11.2-2.1 on GA media","vulnerabilityIds":["CVE-2025-11065","CVE-2025-58058"]},{"id":"openSUSE-SU-2025:15564-1","title":"govulncheck-vulndb-0.0.20250917T170349-1.1 on GA media","vulnerabilityIds":["CVE-2025-4953","CVE-2025-54123","CVE-2025-54376","CVE-2025-58058","CVE-2025-58063","CVE-2025-58157","CVE-2025-58158","CVE-2025-58430","CVE-2025-58437","CVE-2025-58445","CVE-2025-58450","CVE-2025-59358","CVE-2025-59359","CVE-2025-59360","CVE-2025-59361","CVE-2025-7445","CVE-2025-8396","CVE-2025-9072","CVE-2025-9076","CVE-2025-9078","CVE-2025-9084"]},{"id":"openSUSE-SU-2026:20192-1","title":"Security update for tailscale","vulnerabilityIds":["CVE-2025-22869","CVE-2025-58058"]},{"id":"SUSE-SU-2025:21137-1","title":"Security update for alloy","vulnerabilityIds":["CVE-2025-11065","CVE-2025-58058"]},{"id":"openSUSE-SU-2025:15515-1","title":"regclient-0.9.2-1.1 on GA media","vulnerabilityIds":["CVE-2025-58058"]},{"id":"openSUSE-SU-2025:15537-1","title":"warewulf4-4.6.4-1.1 on GA media","vulnerabilityIds":["CVE-2025-58058"]},{"id":"openSUSE-SU-2025:15542-1","title":"trivy-0.66.0-1.1 on GA media","vulnerabilityIds":["CVE-2025-58058"]},{"id":"openSUSE-SU-2025:15508-1","title":"rekor-1.4.1-1.1 on GA media","vulnerabilityIds":["CVE-2025-29923","CVE-2025-58058"]},{"id":"RHSA-2026:37387","title":"Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update","vulnerabilityIds":["CVE-2024-25621","CVE-2024-40635","CVE-2024-45310","CVE-2025-8766","CVE-2025-21613","CVE-2025-21614","CVE-2025-22870","CVE-2025-47911","CVE-2025-52881","CVE-2025-54410","CVE-2025-58058","CVE-2025-64329","CVE-2025-66506","CVE-2026-22772","CVE-2026-23831","CVE-2026-24117","CVE-2026-25680","CVE-2026-25681","CVE-2026-25934","CVE-2026-27136","CVE-2026-27141","CVE-2026-27903","CVE-2026-33540","CVE-2026-33747","CVE-2026-33748","CVE-2026-33814","CVE-2026-34986","CVE-2026-35172","CVE-2026-35469","CVE-2026-39821","CVE-2026-39827","CVE-2026-39828","CVE-2026-39829","CVE-2026-39830","CVE-2026-39831","CVE-2026-39832","CVE-2026-39833","CVE-2026-39834","CVE-2026-39835","CVE-2026-39883","CVE-2026-41506","CVE-2026-41567","CVE-2026-41568","CVE-2026-42502","CVE-2026-42506","CVE-2026-42508","CVE-2026-44740","CVE-2026-45571","CVE-2026-46595","CVE-2026-46597","CVE-2026-46598"]},{"id":"openSUSE-SU-2025:15503-1","title":"tailscale-1.86.5-1.1 on GA media","vulnerabilityIds":["CVE-2025-58058"]},{"id":"openSUSE-SU-2026:11514-1","title":"containerized-data-importer1.66-api-1.66.0-1.1 on GA media","vulnerabilityIds":["CVE-2025-47911","CVE-2025-58058","CVE-2025-58190","CVE-2026-27136","CVE-2026-34986","CVE-2026-35469","CVE-2026-39821","CVE-2026-39827","CVE-2026-39828","CVE-2026-39832","CVE-2026-42508","CVE-2026-56852"]},{"id":"openSUSE-SU-2025:20073-1","title":"Security update for alloy","vulnerabilityIds":["CVE-2025-11065","CVE-2025-58058"]}],"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-2025-26149","identifiers":["EUVD-2025-26149","CVE-2025-58058","GHSA-jc7w-c686-c4v9"]},"retained":false,"historicalAffected":[]},{"revision":"dff19e3347a64811bb85aeff62932244","observedAt":"2026-10-25T03:17:18.142+00:00","statement":{"source":"nvd","id":"CVE-2025-58058","aliases":[],"title":"xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to …","description":"xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.","state":0,"publishedAt":"2025-08-28T22:15:32.577+00:00","modifiedAt":"2026-09-26T00:10:00.127+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","score":5.3,"severity":"MEDIUM"}],"references":["https://github.com/ulikunitz/xz/commit/88ddf1d0d98d688db65de034f48960b2760d2ae2","https://github.com/ulikunitz/xz/security/advisories/GHSA-jc7w-c686-c4v9"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2025-58058","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Deferred","weaknesses":["CWE-770"],"productCriteria":[],"sourceDates":{"published":"2025-08-28T22:15:32.577","lastModified":"2026-09-26T00:10:00.127"},"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-2025-58058","identifiers":["CVE-2025-58058"]},"retained":false,"historicalAffected":[]},{"revision":"bd80f6d013914c1f926835d0157bab53","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-jc7w-c686-c4v9","aliases":["CVE-2025-58058","GO-2025-3922"],"title":"github.com/ulikunitz/xz leaks memory when decoding a corrupted multiple LZMA archives","description":"### Summary\n\nIt is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has  a checksum to detect such an issue according to the [specification](https://github.com/jljusten/LZMA-SDK/blob/master/DOC/lzma-specification.txt).\n\nNote that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done.\n\n### Mitigations\n\nThe release v0.5.15 includes following mitigations:\n\n- The ReaderConfig DictCap field is now interpreted as a limit for the dictionary size.\n- The default is 2 Gigabytes - 1 byte (2^31-1 bytes).\n- Users can check with the [Reader.Header] method what the actual values are in  their LZMA files and set a smaller limit using ReaderConfig.\n- The dictionary size will not exceed the larger of the file size and the minimum dictionary size. This is another measure to prevent huge memory allocations for the dictionary.\n- The code supports stream sizes only up to a pebibyte (1024^5).\n\nNote that the original v0.5.14 version had a compiler error for 32 bit platforms, which has been fixed by v0.5.15.\n\n### Methods affected\n\nOnly software that uses [lzma.NewReader](https://pkg.go.dev/github.com/ulikunitz/xz/lzma#NewReader) or [lzma.ReaderConfig.NewReader](https://pkg.go.dev/github.com/ulikunitz/xz/lzma#ReaderConfig.NewReader) is affected. There is no issue for software using the xz functionality.\n\nI thank  @GregoryBuligin for his report, which is provided below.\n\n### Summary\nWhen unpacking a large number of LZMA archives, even in a single goroutine, if the first byte of the archive file is 0 (a zero byte added to the beginning), an error __writeMatch: distance out of range__ occurs. Memory consumption spikes sharply, and the GC clearly cannot handle this situation.\n\n### Details\nJudging by the error  __writeMatch: distance out of range__, the problems occur in the code around this function.\nhttps://github.com/ulikunitz/xz/blob/c8314b8f21e9c5e25b52da07544cac14db277e89/lzma/decoderdict.go#L81\n\n### PoC\nRun a function similar to this one in 1 or several goroutines on a multitude of LZMA archives that have a 0 (a zero byte) added to the beginning.\n```\nconst ProjectLocalPath = \"some/path\"\nconst TmpDir = \"tmp\"\n\nfunc UnpackLZMA(lzmaFile string) error {\n\tfile, err := os.Open(lzmaFile)\n\tif err != nil {\n\t\treturn err\n\t}\n\tdefer file.Close()\n\n\treader, err := lzma.NewReader(bufio.NewReader(file))\n\tif err != nil {\n\t\treturn err\n\t}\n\n\ttmpFile, err := os.CreateTemp(TmpDir, TmpLZMAPrefix)\n\tif err != nil {\n\t\treturn err\n\t}\n\tdefer func() {\n\t\ttmpFile.Close()\n\t\t_ = os.Remove(tmpFile.Name())\n\t}()\n\n\tsha256Hasher := sha256.New()\n\tmultiWriter := io.MultiWriter(tmpFile, sha256Hasher)\n\n\tif _, err = io.Copy(multiWriter, reader); err != nil {\n\t\treturn err\n\t}\n\n\tunpackHash := hex.EncodeToString(sha256Hasher.Sum(nil))\n\tunpackDir := filepath.Join(\n\t\tProjectLocalPath, unpackHash[:2],\n\t)\n\t_ = os.MkdirAll(unpackDir, DirPerm)\n\n\tunpackPath := filepath.Join(unpackDir, unpackHash)\n\n\treturn os.Rename(tmpFile.Name(), unpackPath)\n}\n```\n\n\n\n### Impact\nServers with a small amount of RAM that download and unpack a large number of unverified LZMA archives","state":0,"publishedAt":"2025-08-28T19:36:22+00:00","modifiedAt":"2026-09-10T03:50:27.1576479+00:00","affected":[{"ecosystem":"Go","name":"github.com/ulikunitz/xz","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"0.5.15"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/ulikunitz/xz/security/advisories/GHSA-jc7w-c686-c4v9","https://nvd.nist.gov/vuln/detail/CVE-2025-58058","https://github.com/ulikunitz/xz/commit/88ddf1d0d98d688db65de034f48960b2760d2ae2","https://github.com/ulikunitz/xz"],"sourceUrl":"https://github.com/advisories/GHSA-jc7w-c686-c4v9","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-jc7w-c686-c4v9","identifiers":["GHSA-jc7w-c686-c4v9","CVE-2025-58058","GO-2025-3922"]},"retained":false,"historicalAffected":[]},{"revision":"5267d3b9f9f14f2ea635fe9cc24111e1","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GO-2025-3922","aliases":["CVE-2025-58058","GHSA-jc7w-c686-c4v9"],"title":"Memory leaks when decoding a corrupted multiple LZMA archives in github.com/ulikunitz/xz","description":"Memory leaks when decoding a corrupted multiple LZMA archives in github.com/ulikunitz/xz","state":0,"publishedAt":"2025-09-17T17:03:38+00:00","modifiedAt":"2026-02-04T03:52:11.088726+00:00","affected":[{"ecosystem":"Go","name":"github.com/ulikunitz/xz","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"0.5.15"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://github.com/ulikunitz/xz/security/advisories/GHSA-jc7w-c686-c4v9","https://github.com/ulikunitz/xz/commit/88ddf1d0d98d688db65de034f48960b2760d2ae2"],"sourceUrl":"https://osv.dev/vulnerability/GO-2025-3922","license":"OSV · upstream source license applies","key":"osv:GO-2025-3922","identifiers":["GO-2025-3922","CVE-2025-58058","GHSA-jc7w-c686-c4v9"]},"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-12T09:55:31.2947259+00:00","complete":true,"records":1779,"lastAttemptAt":"2026-11-12T09:55:31.2947259+00:00","lastSuccessAt":"2026-11-12T09:55:31.4790381+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:55:31.4790388+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-64752486c567b55b31fb0d7225f5222bcd0019564ac0ac5f0649e242c7b19299-96b9449de903276976deb618e1ee304842c062146e687b0fb22bdc2878e043b0","complete":true,"records":424634,"lastAttemptAt":"2026-11-12T09:53:34.7943744+00:00","lastSuccessAt":"2026-11-12T09:53:34.7689851+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:53:34.7943744+00:00","snapshotPublishedAt":"2026-11-12T09:24:42+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-9db698e4659747149ec1092e3d34a5a1","complete":true,"records":13764,"lastAttemptAt":"2026-11-12T09:56:01.66177+00:00","lastSuccessAt":"2026-11-12T09:56:01.656+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:56:01.656+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13817,"expectedIdentifiers":13817,"failedIdentifiers":0},{"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-12T09:55:31.2947259+00:00","complete":true,"records":1097,"lastAttemptAt":"2026-11-12T09:55:31.2947259+00:00","lastSuccessAt":"2026-11-12T09:55:31.4798179+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:55:31.4798182+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-1a7cc780d036453fb794b7d2d385de9d","complete":false,"records":13764,"lastAttemptAt":"2026-11-12T09:55:57.1306222+00:00","lastSuccessAt":"2026-11-12T09:55:57.111+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:55:57.111+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13313,"expectedIdentifiers":13817,"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-3562b6c78fd1bd0f0b55daf66a0926ae24f65e462df7f6d928caad458fc696bf","complete":true,"records":9947,"lastAttemptAt":"2026-11-12T09:55:26.640208+00:00","lastSuccessAt":"2026-11-11T04:27:43.6877707+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:55:26.640208+00:00","snapshotPublishedAt":"2026-11-11T03:32:46+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-456002455e0ab94bb92c95476d4e6d175c104cd594749982afd96c893728ecbc","complete":true,"records":2010,"lastAttemptAt":"2026-11-12T09:53:34.9350012+00:00","lastSuccessAt":"2026-11-11T02:36:58.1276999+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:53:34.9350012+00:00","snapshotPublishedAt":"2026-11-11T01:17:51+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-f46f74c6a30a9b6e4cfb481719c6d35521ebec2d53ebf163223d093ae587eb9d","complete":true,"records":3106,"lastAttemptAt":"2026-11-12T09:55:31.2553322+00:00","lastSuccessAt":"2026-11-12T09:55:31.1176285+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:55:31.2553322+00:00","snapshotPublishedAt":"2026-11-12T09:48:13+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-ef2ecb421099c77d2be989a707f600817e68bbc84b134f8c0b574289c6a9dbb4","complete":true,"records":231700,"lastAttemptAt":"2026-11-12T09:55:26.5140063+00:00","lastSuccessAt":"2026-11-12T09:55:25.0439596+00:00","error":null,"lastVerifiedAt":"2026-11-12T09:55:26.5140063+00:00","snapshotPublishedAt":"2026-11-12T09:33:09+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}