{"id":"GHSA-92mw-q256-5vwg","revision":null,"records":[{"revision":"7f86890097de48da9a6eba2a08500728","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2024-22424","aliases":[],"title":"Cross-Site Request Forgery (CSRF) in github.com/argoproj/argo-cd","description":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The Argo CD API prior to versions 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15 are vulnerable to a cross-server request forgery (CSRF) attack when the attacker has the ability to write HTML to a page on the same parent domain as Argo CD. A CSRF attack works by tricking an authenticated Argo CD user into loading a web page which contains code to call Argo CD API endpoints on the victim’s behalf. For example, an attacker could send an Argo CD user a link to a page which looks harmless but in the background calls an Argo CD API endpoint to create an application running malicious code. Argo CD uses the “Lax” SameSite cookie policy to prevent CSRF attacks where the attacker controls an external domain. The malicious external website can attempt to call the Argo CD API, but the web browser will refuse to send the Argo CD auth token with the request. Many companies host Argo CD on an internal subdomain. If an attacker can place malicious code on, for example, https://test.internal.example.com/, they can still perform a CSRF attack. In this case, the “Lax” SameSite cookie does not prevent the browser from sending the auth cookie, because the destination is a parent domain of the Argo CD API. Browsers generally block such attacks by applying CORS policies to sensitive requests with sensitive content types. Specifically, browsers will send a “preflight request” for POSTs with content type “application/json” asking the destination API “are you allowed to accept requests from my domain?” If the destination API does not answer “yes,” the browser will block the request. Before the patched versions, Argo CD did not validate that requests contained the correct content type header. So an attacker could bypass the browser’s CORS check by setting the content type to something which is considered “not sensitive” such as “text/plain.” The browser wouldn’t send the preflight request, and Argo CD would happily accept the contents (which are actually still JSON) and perform the requested action (such as running malicious code). A patch for this vulnerability has been released in the following Argo CD versions: 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15. The patch contains a breaking API change. The Argo CD API will no longer accept non-GET requests which do not specify application/json as their Content-Type. The accepted content types list is configurable, and it is possible (but discouraged) to disable the content type check completely. Users are advised to upgrade. There are no known workarounds for this vulnerability.","state":0,"publishedAt":"2024-01-19T00:25:44.946+00:00","modifiedAt":"2025-05-30T14:26:48.241+00:00","affected":[{"ecosystem":"Vendor product","name":"argo-cd","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"argoproj\",\n                    \"product\": \"argo-cd\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 0.1.0, < 2.7.15\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 2.8.0, < 2.8.8\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 2.9.0, < 2.9.4\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 2.10.0-rc1, < 2.10-rc2\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","score":8.4,"severity":"HIGH"}],"references":["https://github.com/argoproj/argo-cd/security/advisories/GHSA-92mw-q256-5vwg","https://github.com/argoproj/argo-cd/issues/2496","https://github.com/argoproj/argo-cd/pull/16860"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-22424","license":"CVE Program Terms of Use","key":"cve-program:CVE-2024-22424","identifiers":["CVE-2024-22424"]},"retained":false,"historicalAffected":[]},{"revision":"d416d84b0d344138a04cfa45f772a9f3","observedAt":"2026-11-15T01:48:57.658+00:00","statement":{"source":"euvd","id":"EUVD-2024-0307","aliases":["CVE-2024-22424","GHSA-92mw-q256-5vwg"],"title":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The Argo CD API prior to versions 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15 are vulnerable to a cross-server request forgery (CSRF) attack when the attacker has the ability …","description":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The Argo CD API prior to versions 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15 are vulnerable to a cross-server request forgery (CSRF) attack when the attacker has the ability to write HTML to a page on the same parent domain as Argo CD. A CSRF attack works by tricking an authenticated Argo CD user into loading a web page which contains code to call Argo CD API endpoints on the victim’s behalf. For example, an attacker could send an Argo CD user a link to a page which looks harmless but in the background calls an Argo CD API endpoint to create an application running malicious code. Argo CD uses the “Lax” SameSite cookie policy to prevent CSRF attacks where the attacker controls an external domain. The malicious external website can attempt to call the Argo CD API, but the web browser will refuse to send the Argo CD auth token with the request. Many companies host Argo CD on an internal subdomain. If an attacker can place malicious code on, for example, https://test.internal.example.com/, they can still perform a CSRF attack. In this case, the “Lax” SameSite cookie does not prevent the browser from sending the auth cookie, because the destination is a parent domain of the Argo CD API. Browsers generally block such attacks by applying CORS policies to sensitive requests with sensitive content types. Specifically, browsers will send a “preflight request” for POSTs with content type “application/json” asking the destination API “are you allowed to accept requests from my domain?” If the destination API does not answer “yes,” the browser will block the request. Before the patched versions, Argo CD did not validate that requests contained the correct content type header. So an attacker could bypass the browser’s CORS check by setting the content type to something which is considered “not sensitive” such as “text/plain.” The browser wouldn’t send the preflight request, and Argo CD would happily accept the contents (which are actually still JSON) and perform the requested action (such as running malicious code). A patch for this vulnerability has been released in the following Argo CD versions: 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15. The patch contains a breaking API change. The Argo CD API will no longer accept non-GET requests which do not specify application/json as their Content-Type. The accepted content types list is configurable, and it is possible (but discouraged) to disable the content type check completely. Users are advised to upgrade. There are no known workarounds for this vulnerability.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","score":8.4,"severity":null}],"references":["https://github.com/argoproj/argo-cd/security/advisories/GHSA-92mw-q256-5vwg","https://github.com/argoproj/argo-cd/issues/2496","https://github.com/argoproj/argo-cd/pull/16860"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-0307","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Jan 19, 2024, 12:25:44 AM","dateUpdated":"May 30, 2025, 2:26:48 PM"},"relatedAdvisories":[{"id":"RHSA-2024:0692","title":"Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps 1.10.2 security update","vulnerabilityIds":["CVE-2023-49568","CVE-2023-49569","CVE-2024-22424"]},{"id":"RHSA-2024:0689","title":"Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps 1.11.1 security update","vulnerabilityIds":["CVE-2024-22424"]},{"id":"WID-SEC-W-2024-0697","title":"Red Hat OpenShift: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen","vulnerabilityIds":["CVE-2024-22424"]},{"id":"RHSA-2024:0691","title":"Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps v1.9.4 security update","vulnerabilityIds":["CVE-2023-49568","CVE-2023-49569","CVE-2024-22424"]}],"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-2024-0307","identifiers":["EUVD-2024-0307","CVE-2024-22424","GHSA-92mw-q256-5vwg"]},"retained":false,"historicalAffected":[]},{"revision":"4662bcba566e4fb1a3534d691e53ef2b","observedAt":"2026-10-24T23:17:22.571+00:00","statement":{"source":"nvd","id":"CVE-2024-22424","aliases":[],"title":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The Argo CD API prior to versions 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15 are vulnerable to a cross-server request forgery (CSRF) attack when the attacker has the ability …","description":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The Argo CD API prior to versions 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15 are vulnerable to a cross-server request forgery (CSRF) attack when the attacker has the ability to write HTML to a page on the same parent domain as Argo CD. A CSRF attack works by tricking an authenticated Argo CD user into loading a web page which contains code to call Argo CD API endpoints on the victim’s behalf. For example, an attacker could send an Argo CD user a link to a page which looks harmless but in the background calls an Argo CD API endpoint to create an application running malicious code. Argo CD uses the “Lax” SameSite cookie policy to prevent CSRF attacks where the attacker controls an external domain. The malicious external website can attempt to call the Argo CD API, but the web browser will refuse to send the Argo CD auth token with the request. Many companies host Argo CD on an internal subdomain. If an attacker can place malicious code on, for example, https://test.internal.example.com/, they can still perform a CSRF attack. In this case, the “Lax” SameSite cookie does not prevent the browser from sending the auth cookie, because the destination is a parent domain of the Argo CD API. Browsers generally block such attacks by applying CORS policies to sensitive requests with sensitive content types. Specifically, browsers will send a “preflight request” for POSTs with content type “application/json” asking the destination API “are you allowed to accept requests from my domain?” If the destination API does not answer “yes,” the browser will block the request. Before the patched versions, Argo CD did not validate that requests contained the correct content type header. So an attacker could bypass the browser’s CORS check by setting the content type to something which is considered “not sensitive” such as “text/plain.” The browser wouldn’t send the preflight request, and Argo CD would happily accept the contents (which are actually still JSON) and perform the requested action (such as running malicious code). A patch for this vulnerability has been released in the following Argo CD versions: 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15. The patch contains a breaking API change. The Argo CD API will no longer accept non-GET requests which do not specify application/json as their Content-Type. The accepted content types list is configurable, and it is possible (but discouraged) to disable the content type check completely. Users are advised to upgrade. There are no known workarounds for this vulnerability.","state":0,"publishedAt":"2024-01-19T01:15:09.317+00:00","modifiedAt":"2026-06-17T07:11:23.167+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","score":8.3,"severity":"HIGH"},{"system":"CVSS 3.1 · nvd@nist.gov · Primary","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","score":8.3,"severity":"HIGH"}],"references":["https://github.com/argoproj/argo-cd/issues/2496","https://github.com/argoproj/argo-cd/pull/16860","https://github.com/argoproj/argo-cd/security/advisories/GHSA-92mw-q256-5vwg"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2024-22424","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Modified","weaknesses":["CWE-352"],"productCriteria":["cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*","cpe:2.3:a:argoproj:argo_cd:2.10.0:rc1:*:*:*:*:*:*","cpe:2.3:a:linuxfoundation:argo-cd:*:*:*:*:*:*:*:*"],"sourceDates":{"published":"2024-01-19T01:15:09.317","lastModified":"2026-06-17T07:11:23.167"},"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-22424","identifiers":["CVE-2024-22424"]},"retained":false,"historicalAffected":[]},{"revision":"05870446fe354e13841a7b1435ec99f5","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-92mw-q256-5vwg","aliases":["CVE-2024-22424"],"title":"github.com/argoproj/argo-cd Cross-Site Request Forgery vulnerability","description":"### Impact\n\nThe Argo CD API prior to versions 2.10-rc2, 2.9.4, 2.8.8, and 2.7.16 are vulnerable to a cross-server request forgery (CSRF) attack when the attacker has the ability to write HTML to a page on the same parent domain as Argo CD.\n\nA CSRF attack works by tricking an authenticated Argo CD user into loading a web page which contains code to call Argo CD API endpoints on the victim’s behalf. For example, an attacker could send an Argo CD user a link to a page which looks harmless but in the background calls an Argo CD API endpoint to create an application running malicious code.\n\nArgo CD uses the “Lax” SameSite cookie policy to prevent CSRF attacks where the attacker controls an external domain. The malicious external website can attempt to call the Argo CD API, but the web browser will refuse to send the Argo CD auth token with the request.\n\nMany companies host Argo CD on an internal subdomain, such as [https://argo-cd.internal.example.com](https://argo-cd.example.com/). If an attacker can place malicious code on, for example, https://test.internal.example.com/, they can still perform a CSRF attack. In this case, the “Lax” SameSite cookie does not prevent the browser from sending the auth cookie, because the destination is a parent domain of the Argo CD API.\n\nBrowsers generally block such attacks by applying CORS policies to sensitive requests with sensitive content types. Specifically, browsers will send a “preflight request” for POSTs with content type “application/json” asking the destination API “are you allowed to accept requests from my domain?” If the destination API does not answer “yes,” the browser will block the request.\n\nBefore the patched versions, Argo CD did not validate that requests contained the correct content type header. So an attacker could bypass the browser’s CORS check by setting the content type to something which is considered “not sensitive” such as “text/plain.” The browser wouldn’t send the preflight request, and Argo CD would happily accept the contents (which are actually still JSON) and perform the requested action (such as running malicious code).\n\n### Patches\n\nA patch for this vulnerability has been released in the following Argo CD versions:\n\n* 2.10-rc2\n* 2.9.4\n* 2.8.8\n* 2.7.16\n\n\uD83D\uDEA8 **The patch contains a breaking API change.** \uD83D\uDEA8 The Argo CD API will no longer accept non-GET requests which do not specify application/json as their Content-Type. The accepted content types list is configurable, and it is possible (but discouraged) to disable the content type check completely.\n\n### Workarounds\n\nThe only way to completely resolve the issue is to upgrade.\n\n### Credits\n\nThe Argo CD team would like to express their gratitude to An Trinh of [Calif](https://calif.io/) who reported the issue confidentially according to our [guidelines](https://github.com/argoproj/argo-cd/blob/master/SECURITY.md#reporting-a-vulnerability) and published a helpful [blog post](https://blog.calif.io/p/argo-cd-csrf) to describe the issue. We would also like to thank them for actively participating in the review for the patch.\n\n### References\n\n* The problem was originally reported in a [GitHub issue](https://github.com/argoproj/argo-cd/issues/2496)","state":0,"publishedAt":"2024-01-19T20:37:53+00:00","modifiedAt":"2026-09-10T03:50:09.2849776+00:00","affected":[{"ecosystem":"Go","name":"github.com/argoproj/argo-cd","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.1.0"},{"kind":"last_affected","version":"1.8.7"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/argoproj/argo-cd/v2","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"2.7.16"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/argoproj/argo-cd/v2","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"2.8.0-rc1"},{"kind":"fixed","version":"2.8.8"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/argoproj/argo-cd/v2","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"2.9.0-rc1"},{"kind":"fixed","version":"2.9.4"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/argoproj/argo-cd/v2","ranges":[{"type":"ECOSYSTEM","events":[{"kind":"introduced","version":"2.10.0-rc1"},{"kind":"fixed","version":"2.10-rc2"}]}],"versions":["2.10.0-rc1"],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/argoproj/argo-cd/security/advisories/GHSA-92mw-q256-5vwg","https://nvd.nist.gov/vuln/detail/CVE-2024-22424","https://github.com/argoproj/argo-cd/issues/2496","https://github.com/argoproj/argo-cd/pull/16860","https://github.com/argoproj/argo-cd/commit/0b459f224b3186707809be8240dfc3a6028f42a0","https://github.com/argoproj/argo-cd/commit/13fe3ca589f6f2ded6001ce114e354602ed058b3","https://github.com/argoproj/argo-cd/commit/3c5878ecf41581942281e9c95745f073bdfbf9c3","https://github.com/argoproj/argo-cd/commit/f569aa105e0fe5940bc736c68e2fc90ee4a6ed94","https://github.com/argoproj/argo-cd"],"sourceUrl":"https://github.com/advisories/GHSA-92mw-q256-5vwg","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-92mw-q256-5vwg","identifiers":["GHSA-92mw-q256-5vwg","CVE-2024-22424"]},"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-16T14:44:51.0354681+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-16T14:44:51.0354681+00:00","lastSuccessAt":"2026-11-16T14:44:51.2191988+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:51.2191997+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-c7e42aebd80e0c2307ddc550ecef29877d1c8891eaea04fabfc75498ab1ffe9c","complete":true,"records":426004,"lastAttemptAt":"2026-11-16T14:44:50.7345962+00:00","lastSuccessAt":"2026-11-16T14:44:50.6847077+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:50.7345962+00:00","snapshotPublishedAt":"2026-11-16T14:31:19+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-e7b8d43557f44ad0b4e0a87d8bc9833b","complete":true,"records":13821,"lastAttemptAt":"2026-11-16T14:45:17.0377344+00:00","lastSuccessAt":"2026-11-16T13:45:32.439+00:00","error":null,"lastVerifiedAt":"2026-11-16T13:45:32.439+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13874,"expectedIdentifiers":13874,"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-16T14:44:51.0354681+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-16T14:44:51.0354681+00:00","lastSuccessAt":"2026-11-16T14:44:51.2200779+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:51.2200784+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-4b206dc3f3fc4572b101aa266f730110","complete":false,"records":13833,"lastAttemptAt":"2026-11-16T14:45:16.4505777+00:00","lastSuccessAt":"2026-11-16T14:45:16.447+00:00","error":"300 identifier lookups failed; latest failures include HttpError (HTTP 503). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T14:45:16.447+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13574,"expectedIdentifiers":13874,"failedIdentifiers":300},{"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-16T14:44:50.9903861+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:50.9903861+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-16T14:44:50.781369+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:50.781369+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-16T14:44:51.0024803+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:51.0024803+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-263d9c8d63997345727b11314d9b9377eba9fd4146f04497c069a15e332b60cb","complete":true,"records":232482,"lastAttemptAt":"2026-11-16T14:44:50.8876074+00:00","lastSuccessAt":"2026-11-16T07:32:30.5701252+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:50.8876074+00:00","snapshotPublishedAt":"2026-11-16T06:48:00+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}