Assign IDs

Author: github-actions

advisories/.id-allocator

@@ -1 +1 @@
-73f31ee892729d4843b1ffc2ec75af21d180cb5748ba332362e738bdef2007b4
+f93f4db8bc5726c5433e1cc0654caeefd0366015589c72961d91fcfb0f1fc882

…ories/python/PSF-0000-CVE-2025-8291.json advisories/python/PSF-2025-12.jsonadvisories/python/PSF-0000-CVE-2025-8291.json renamed to advisories/python/PSF-2025-12.json advisories/python/PSF-0000-CVE-2025-8291.json renamed to advisories/python/PSF-2025-12.json

@@ -1,11 +1,11 @@
 {
+  "modified": "2025-10-07T18:22:46Z",
+  "published": "2025-10-07T18:10:05Z",
   "schema_version": "1.5.0",
-  "id": "PSF-0000-CVE-2025-8291",
+  "id": "PSF-2025-12",
   "aliases": [
     "CVE-2025-8291"
   ],
-  "published": "2025-10-07T18:10:05.908Z",
-  "modified": "2025-10-07T18:22:46.912Z",
   "details": "The 'zipfile' module would not check the validity of the ZIP64 End of\nCentral Directory (EOCD) Locator record offset value would not be used to\nlocate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be\nassumed to be the previous record in the ZIP archive. This could be abused\nto create ZIP archives that are handled differently by the 'zipfile' module\ncompared to other ZIP implementations.\n\n\nRemediation maintains this behavior, but checks that the offset specified\nin the ZIP64 EOCD Locator record matches the expected value.",
   "affected": [
     {
@@ -53,4 +53,4 @@
   "database_specific": {
     "cwe_ids": []
   }
-}
+}