{"metadata": {"vulnerability": "cve-2025-31484", "count": 15, "kinds": {"milestone": 3, "sighting": 6, "kev": 0, "other": 6}}, "data": [{"timestamp": "2025-03-28T13:36:51.297Z", "date_only": false, "value": "2025-03-28T13:36:51.297Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "cve-2025-31484", "field": "cveMetadata.dateReserved"}, {"timestamp": "2025-04-02T21:38:03.493Z", "date_only": false, "value": "2025-04-02T21:38:03.493Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "cve-2025-31484", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2025-04-02T21:38:03.493Z", "date_only": false, "value": "2025-04-02T21:38:03.493Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / GitHub_M", "record": "cve-2025-31484", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2025-04-02T22:11:54.289Z", "date_only": false, "value": "2025-04-02T22:11:54.289319Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cR0w/statuses/114270661068874157", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "207d8033-1e72-4761-a5e5-48befe24faa8", "url": "https://infosec.exchange/users/cR0w/statuses/114270661068874157"}, {"timestamp": "2025-04-02T22:11:54.290Z", "date_only": false, "value": "2025-04-02T22:11:54.290376Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cR0w/statuses/114270661068874157", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "5648378e-2984-4bbd-ab87-986c5ba02610", "url": "https://infosec.exchange/users/cR0w/statuses/114270661068874157"}, {"timestamp": "2025-04-02T22:15:20.720Z", "date_only": false, "value": "2025-04-02T22:15:20.720", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2025-31484", "record": "FKIE_CVE-2025-31484", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2025-04-02T22:34:43Z", "date_only": false, "value": "2025-04-02T22:34:43.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10155", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "df5648fc-2b3b-4a1e-b4e2-c1d05ad985d2", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-31484\n\ud83d\udd25 CVSS Score: 9.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.\nBetween 2025-02-10 and 2025-04-01, conda-forge infrastructure used the wrong token for Azure's cf-staging access. This bug meant that any feedstock maintainer could upload a package to the conda-forge channel, bypassing our feedstock-token + upload process. The security logs on anaconda.org were check for any packages that were not copied from the cf-staging to the conda-forge channel and none were found.\n\ud83d\udccf Published: 2025-04-02T21:38:03.493Z\n\ud83d\udccf Modified: 2025-04-02T21:38:03.493Z\n\ud83d\udd17 References:\n1. https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72\n2. https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052", "url": "https://t.me/DarkWebInformer_CVEAlerts/10155", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}, {"timestamp": "2025-04-02T22:40:25.108Z", "date_only": false, "value": "2025-04-02T22:40:25.108371Z", "kind": "sighting", "label": "Seen", "source": "https://bsky.app/profile/cyberalerts.bsky.social/post/3lluhfgnjdx2s", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "f442e34c-1ed3-4623-96a8-0485d7faa490", "url": "https://bsky.app/profile/cyberalerts.bsky.social/post/3lluhfgnjdx2s"}, {"timestamp": "2025-04-02T23:01:29.820Z", "date_only": false, "value": "2025-04-02T23:01:29.820234Z", "kind": "sighting", "label": "Seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lluikvpbh22w", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "0da8d3b7-6df3-4d9e-85ed-93498ddd283f", "url": "https://bsky.app/profile/cve.skyfleet.blue/post/3lluikvpbh22w"}, {"timestamp": "2025-04-03T01:01:24Z", "date_only": false, "value": "2025-04-03T01:01:24.000000Z", "kind": "sighting", "label": "Seen", "source": "https://t.me/cvedetector/21918", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "20a53f13-a28c-4ca3-85f6-6120894286e8", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-31484 - Conda-Forge Azure CF-Staging Token Exposure\", \n  \"Content\": \"CVE ID : CVE-2025-31484 \nPublished : April 2, 2025, 10:15 p.m. | 20\u00a0minutes ago \nDescription : conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.  \nBetween 2025-02-10 and 2025-04-01, conda-forge infrastructure used the wrong token for Azure's cf-staging access. This bug meant that any feedstock maintainer could upload a package to the conda-forge channel, bypassing our feedstock-token + upload process. The security logs on anaconda.org were check for any packages that were not copied from the cf-staging to the conda-forge channel and none were found. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "url": "https://t.me/cvedetector/21918"}, {"timestamp": "2025-04-03T19:35:06.236Z", "date_only": false, "value": "2025-04-03T19:35:06.236135Z", "kind": "other", "label": "Recorded", "source": "cvelistv5 / CISA-ADP", "record": "cve-2025-31484", "field": "containers.adp.0.metrics.0.other.content.timestamp"}, {"timestamp": "2025-04-03T19:35:06.236Z", "date_only": false, "value": "2025-04-03T19:35:06.236135Z", "kind": "other", "label": "Recorded", "source": "fkie_nvd \u00b7 FKIE_CVE-2025-31484", "record": "FKIE_CVE-2025-31484", "field": "metrics.ssvcV203.0.ssvcData.timestamp", "linked_record": true}, {"timestamp": "2025-04-03T19:38:18.563Z", "date_only": false, "value": "2025-04-03T19:38:18.563Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "cve-2025-31484", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2025-04-03T19:38:18.563Z", "date_only": false, "value": "2025-04-03T19:38:18.563Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / CISA-ADP", "record": "cve-2025-31484", "field": "containers.adp.0.providerMetadata.dateUpdated"}, {"timestamp": "2026-06-17T09:10:28.960Z", "date_only": false, "value": "2026-06-17T09:10:28.960", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2025-31484", "record": "FKIE_CVE-2025-31484", "field": "lastModified", "linked_record": true}], "metrics": {"as_of": "2026-11-15T05:41:32.613Z", "anchors": {"origin": {"timestamp": "2025-04-02T21:38:03.493Z", "date_only": false, "value": "2025-04-02T21:38:03.493Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "cve-2025-31484", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2025-04-02T21:38:03.493Z", "date_only": false, "value": "2025-04-02T21:38:03.493Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "cve-2025-31484", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": {"timestamp": "2025-04-02T22:34:43Z", "date_only": false, "value": "2025-04-02T22:34:43.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10155", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "df5648fc-2b3b-4a1e-b4e2-c1d05ad985d2", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-31484\n\ud83d\udd25 CVSS Score: 9.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.\nBetween 2025-02-10 and 2025-04-01, conda-forge infrastructure used the wrong token for Azure's cf-staging access. This bug meant that any feedstock maintainer could upload a package to the conda-forge channel, bypassing our feedstock-token + upload process. The security logs on anaconda.org were check for any packages that were not copied from the cf-staging to the conda-forge channel and none were found.\n\ud83d\udccf Published: 2025-04-02T21:38:03.493Z\n\ud83d\udccf Modified: 2025-04-02T21:38:03.493Z\n\ud83d\udd17 References:\n1. https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72\n2. https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052", "url": "https://t.me/DarkWebInformer_CVEAlerts/10155", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": true, "seconds": 3399.507, "hours": 0.9443075, "days": 0.03934614583333333, "min_seconds": 3399.507, "max_seconds": 3399.507, "approximate": false, "ongoing": false, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2025-04-02T21:38:03.493Z", "date_only": false, "value": "2025-04-02T21:38:03.493Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "cve-2025-31484", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2025-04-02T22:34:43Z", "date_only": false, "value": "2025-04-02T22:34:43.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10155", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "df5648fc-2b3b-4a1e-b4e2-c1d05ad985d2", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-31484\n\ud83d\udd25 CVSS Score: 9.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.\nBetween 2025-02-10 and 2025-04-01, conda-forge infrastructure used the wrong token for Azure's cf-staging access. This bug meant that any feedstock maintainer could upload a package to the conda-forge channel, bypassing our feedstock-token + upload process. The security logs on anaconda.org were check for any packages that were not copied from the cf-staging to the conda-forge channel and none were found.\n\ud83d\udccf Published: 2025-04-02T21:38:03.493Z\n\ud83d\udccf Modified: 2025-04-02T21:38:03.493Z\n\ud83d\udd17 References:\n1. https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72\n2. https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052", "url": "https://t.me/DarkWebInformer_CVEAlerts/10155", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 51091409.12045, "hours": 14192.058089013888, "days": 591.335753708912, "min_seconds": 51091409.12045, "max_seconds": 51091409.12045, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2025-04-02T21:38:03.493Z", "date_only": false, "value": "2025-04-02T21:38:03.493Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "cve-2025-31484", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-15T05:41:32.613Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": true, "seconds": 51088009.61345, "hours": 14191.113781513888, "days": 591.2964075630787, "min_seconds": 51088009.61345, "max_seconds": 51088009.61345, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2025-04-02T22:34:43Z", "date_only": false, "value": "2025-04-02T22:34:43.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10155", "record": "CVE-2025-31484", "field": "creation_timestamp", "uuid": "df5648fc-2b3b-4a1e-b4e2-c1d05ad985d2", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-31484\n\ud83d\udd25 CVSS Score: 9.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.\nBetween 2025-02-10 and 2025-04-01, conda-forge infrastructure used the wrong token for Azure's cf-staging access. This bug meant that any feedstock maintainer could upload a package to the conda-forge channel, bypassing our feedstock-token + upload process. The security logs on anaconda.org were check for any packages that were not copied from the cf-staging to the conda-forge channel and none were found.\n\ud83d\udccf Published: 2025-04-02T21:38:03.493Z\n\ud83d\udccf Modified: 2025-04-02T21:38:03.493Z\n\ud83d\udd17 References:\n1. https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72\n2. https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052", "url": "https://t.me/DarkWebInformer_CVEAlerts/10155", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}, "end": {"timestamp": "2026-11-15T05:41:32.613Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}}}