{"id":"GHSA-c827-hfw6-qwvm","revision":null,"records":[{"revision":"0b68b85eac7a49e2bca3d22bdbf8f7a8","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2024-43806","aliases":[],"title":"`rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion","description":"Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it's possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion. As an example, Linux's various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors. An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue.","state":0,"publishedAt":"2024-08-26T18:43:22.626+00:00","modifiedAt":"2024-08-26T19:40:46.911+00:00","affected":[{"ecosystem":"Vendor product","name":"rustix","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"bytecodealliance\",\n                    \"product\": \"rustix\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 0.35.11, < 0.35.15\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 0.36.0, < 0.36.16\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 0.37.0, < 0.37.25\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 0.38.0, < 0.38.19\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm","https://github.com/imsnif/bandwhich/issues/284"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-43806","license":"CVE Program Terms of Use","key":"cve-program:CVE-2024-43806","identifiers":["CVE-2024-43806"]},"retained":false,"historicalAffected":[]},{"revision":"1fd24255a84047dea08147f5677dc6d4","observedAt":"2026-11-15T02:34:27.26+00:00","statement":{"source":"euvd","id":"EUVD-2023-2715","aliases":["CVE-2024-43806","GHSA-c827-hfw6-qwvm"],"title":"Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it's possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue…","description":"Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it's possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion. As an example, Linux's various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors. An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","score":6.5,"severity":null}],"references":["https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm","https://github.com/imsnif/bandwhich/issues/284"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2023-2715","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Aug 26, 2024, 6:43:22 PM","dateUpdated":"Aug 26, 2024, 7:40:46 PM"},"relatedAdvisories":[{"id":"SUSE-SU-2025:02809-1","title":"Security update for rust-keylime","vulnerabilityIds":["CVE-2023-26964","CVE-2024-12224","CVE-2024-32650","CVE-2024-43806","CVE-2025-3416","CVE-2025-58266"]},{"id":"SUSE-SU-2025:02810-1","title":"Security update for rust-keylime","vulnerabilityIds":["CVE-2023-26964","CVE-2024-12224","CVE-2024-32650","CVE-2024-43806","CVE-2025-3416","CVE-2025-58266"]},{"id":"SUSE-SU-2024:3404-1","title":"Security update for rage-encryption","vulnerabilityIds":["CVE-2024-43806"]},{"id":"openSUSE-SU-2024:14354-1","title":"rage-encryption-0.10.0+0-3.1 on GA media","vulnerabilityIds":["CVE-2024-43806"]},{"id":"SUSE-SU-2025:4411-1","title":"Security update for librsvg","vulnerabilityIds":["CVE-2024-12224","CVE-2024-43806"]},{"id":"SUSE-SU-2025:20858-1","title":"Security update for rust-keylime","vulnerabilityIds":["CVE-2024-12224","CVE-2024-43806","CVE-2024-58266","CVE-2025-3416","CVE-2025-55159"]},{"id":"openSUSE-SU-2025:15294-1","title":"keylime-ima-policy-0.2.7+70-2.1 on GA media","vulnerabilityIds":["CVE-2024-12224","CVE-2024-43806"]},{"id":"openSUSE-SU-2026:20396-1","title":"Security update for librsvg","vulnerabilityIds":["CVE-2024-12224","CVE-2024-43806"]},{"id":"openSUSE-SU-2024:14306-1","title":"389-ds-3.1.1~git13.a9c7ff9-1.1 on GA media","vulnerabilityIds":["CVE-2024-43806"]},{"id":"SUSE-SU-2025:20057-1","title":"Security update for rust-keylime","vulnerabilityIds":["CVE-2024-32650","CVE-2024-43806"]},{"id":"msrc_CVE-2024-43806","title":"`rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion","vulnerabilityIds":["CVE-2024-43806"]},{"id":"SUSE-SU-2025:02811-1","title":"Security update for rust-keylime","vulnerabilityIds":["CVE-2023-26964","CVE-2024-12224","CVE-2024-32650","CVE-2024-43806","CVE-2025-3416","CVE-2025-58266"]},{"id":"SUSE-SU-2026:20910-1","title":"Security update for librsvg","vulnerabilityIds":["CVE-2024-12224","CVE-2024-43806"]},{"id":"SUSE-SU-2026:20755-1","title":"Security update for librsvg","vulnerabilityIds":["CVE-2024-12224","CVE-2024-43806"]}],"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-2023-2715","identifiers":["EUVD-2023-2715","CVE-2024-43806","GHSA-c827-hfw6-qwvm"]},"retained":false,"historicalAffected":[]},{"revision":"6647c5e925bb4f1bbd2c5e147bbce4a0","observedAt":"2026-10-25T00:17:28.27+00:00","statement":{"source":"nvd","id":"CVE-2024-43806","aliases":[],"title":"Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it's possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue…","description":"Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it's possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion. As an example, Linux's various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors. An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue.","state":0,"publishedAt":"2024-08-26T19:15:08.19+00:00","modifiedAt":"2026-06-17T07:51:44.96+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm","https://github.com/imsnif/bandwhich/issues/284"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2024-43806","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Deferred","weaknesses":["CWE-400"],"productCriteria":[],"sourceDates":{"published":"2024-08-26T19:15:08.190","lastModified":"2026-06-17T07:51:44.960"},"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-2024-43806","identifiers":["CVE-2024-43806"]},"retained":false,"historicalAffected":[]},{"revision":"96bb792ef10246eb8aa491274e6831af","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-c827-hfw6-qwvm","aliases":["CVE-2024-43806"],"title":"rustix's `rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion","description":"### Summary\n\nWhen using `rustix::fs::Dir` using the `linux_raw` backend, it's possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application.\n\n### Details\n\n#### Discovery\n\nThe symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. See [this post](https://github.com/imsnif/bandwhich/issues/284#issuecomment-1754321993) and the [Discord thread](https://discord.com/channels/273534239310479360/1161137828395237556) for details.\n\n#### Diagnosis\n\nThis issue is caused by the combination of two independent bugs:\n\n1. Stuck iterator\n- The `rustix::fs::Dir` iterator can fail to halt after encountering an IO error, causing the caller to be stuck in an infinite loop.\n2. Memory over-allocation\n- `Dir::read_more` incorrectly grows the read buffer unconditionally each time it is called, regardless of necessity.\n\nSince `<Dir as Iterator>::next` calls `Dir::read`, which in turn calls `Dir::read_more`, this means an IO error encountered during reading a directory can lead to rapid and unbounded growth of memory use.\n\n### PoC\n\n```rust\nfn main() -> Result<(), Box<dyn std::error::Error>> {\n    // create a directory, get a FD to it, then unlink the directory but keep the FD\n    std::fs::create_dir(\"tmp_dir\")?;\n    let dir_fd = rustix::fs::openat(\n        rustix::fs::CWD,\n        rustix::cstr!(\"tmp_dir\"),\n        rustix::fs::OFlags::RDONLY | rustix::fs::OFlags::CLOEXEC,\n        rustix::fs::Mode::empty(),\n    )?;\n    std::fs::remove_dir(\"tmp_dir\")?;\n\n    // iterator gets stuck in infinite loop and memory explodes\n    rustix::fs::Dir::read_from(dir_fd)?\n        // the iterator keeps returning `Some(Err(_))`, but never halts by returning `None`\n        // therefore if the implementation ignores the error (or otherwise continues\n        // after seeing the error instead of breaking), the loop will not halt\n        .filter_map(|dirent_maybe_error| dirent_maybe_error.ok())\n        .for_each(|dirent| {\n            // your happy path\n            println!(\"{dirent:?}\");\n        });\n\n    Ok(())\n}\n```\n\n### Impact\n\nIf a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion.\n\nAs an example, Linux's various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors.\n\nAn attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service.","state":0,"publishedAt":"2023-10-18T18:27:47+00:00","modifiedAt":"2026-09-10T03:50:03.698097+00:00","affected":[{"ecosystem":"crates.io","name":"rustix","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.35.11"},{"kind":"fixed","version":"0.35.15"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"rustix","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.36.0"},{"kind":"fixed","version":"0.36.16"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"rustix","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.37.0"},{"kind":"fixed","version":"0.37.25"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"rustix","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.38.0"},{"kind":"fixed","version":"0.38.19"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm","https://nvd.nist.gov/vuln/detail/CVE-2024-43806","https://github.com/imsnif/bandwhich/issues/284","https://github.com/imsnif/bandwhich/issues/284#issuecomment-1754321993","https://github.com/bytecodealliance/rustix/commit/31fd98ca723b93cc6101a3e29843ea5cf094e159","https://github.com/bytecodealliance/rustix/commit/87481a97f4364d12d5d6f30cdd025a0fc509b8ec","https://github.com/bytecodealliance/rustix/commit/df3c3a192cf144af0da8a57417fb4addbdc611f6","https://github.com/bytecodealliance/rustix/commit/eecece4a84fc58eafdc809cc2cedd374dee876a5","https://discord.com/channels/273534239310479360/1161137828395237556","https://github.com/bytecodealliance/rustix"],"sourceUrl":"https://github.com/advisories/GHSA-c827-hfw6-qwvm","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-c827-hfw6-qwvm","identifiers":["GHSA-c827-hfw6-qwvm","CVE-2024-43806"]},"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-16T15:46:28.5867679+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-16T15:46:28.5867679+00:00","lastSuccessAt":"2026-11-16T15:46:28.7336518+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.7336528+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-6be044d0e08779dadd136f949a536de4047af96f5d7bceb7e190ecffbb8f18ca-12f82bfd2f0251f244474ead94aa147d6e6e5a295312f7bfcd9f3990dddcf44d","complete":true,"records":426048,"lastAttemptAt":"2026-11-16T15:44:51.0968416+00:00","lastSuccessAt":"2026-11-16T15:44:51.0015391+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:44:51.0968416+00:00","snapshotPublishedAt":"2026-11-16T15:30:52+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-b53a453bd21948638a37a0c1d9db90a8","complete":true,"records":13830,"lastAttemptAt":"2026-11-16T15:47:10.0420289+00:00","lastSuccessAt":"2026-11-16T15:47:10.038+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:47:10.038+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13883,"expectedIdentifiers":13883,"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-16T15:46:28.5867679+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-16T15:46:28.5867679+00:00","lastSuccessAt":"2026-11-16T15:46:28.7348718+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.7348721+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-9aad64c357a84d2b95eb370a9099d8a7","complete":false,"records":13842,"lastAttemptAt":"2026-11-16T15:46:54.2697305+00:00","lastSuccessAt":"2026-11-16T15:46:54.266+00:00","error":"209 identifier lookups failed; latest failures include HttpError (HTTP 503). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T15:46:54.266+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13674,"expectedIdentifiers":13883,"failedIdentifiers":209},{"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-64eea06dbd27de8464d5dbce1b78cc794cc59e2d901516ae0d3ea76e624cdae0","complete":true,"records":9955,"lastAttemptAt":"2026-11-16T15:46:28.4519077+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.4519077+00:00","snapshotPublishedAt":"2026-11-14T13:17:57+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-16T15:44:51.2546448+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:44:51.2546448+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-6086d649bcb454cdf302d7d9275177bda73550e1b6e446b3520e9b6266d3582c","complete":true,"records":3148,"lastAttemptAt":"2026-11-16T15:46:28.5571571+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.5571571+00:00","snapshotPublishedAt":"2026-11-15T10:03:04+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-58b43c63da2e2d496e2f653c5bea97bd9deda68f62d1c3a4dc0212d13b04b5b2","complete":true,"records":232492,"lastAttemptAt":"2026-11-16T15:46:28.326888+00:00","lastSuccessAt":"2026-11-16T15:46:27.3875263+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.326888+00:00","snapshotPublishedAt":"2026-11-16T15:33:39+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}