https://vulnerability.circl.lu/sightings/feed 2026-07-19T07:44:54.469153+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/20a53f13-a28c-4ca3-85f6-6120894286e8/export 2026-07-19T07:44:54.484678+00:00 Automation user https://cvepremium.circl.lu/user/automation {"uuid": "20a53f13-a28c-4ca3-85f6-6120894286e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31484", "type": "seen", "source": "https://t.me/cvedetector/21918", "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", "creation_timestamp": "2025-04-03T01:01:24.000000Z"} 2025-04-03T01:01:24+00:00 https://vulnerability.circl.lu/sighting/0da8d3b7-6df3-4d9e-85ed-93498ddd283f/export 2026-07-19T07:44:54.487820+00:00 Automation user https://cvepremium.circl.lu/user/automation {"uuid": "0da8d3b7-6df3-4d9e-85ed-93498ddd283f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31484", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lluikvpbh22w", "content": "", "creation_timestamp": "2025-04-02T23:01:29.820234Z"} 2025-04-02T23:01:29.820234+00:00 https://vulnerability.circl.lu/sighting/f442e34c-1ed3-4623-96a8-0485d7faa490/export 2026-07-19T07:44:54.488184+00:00 Automation user https://cvepremium.circl.lu/user/automation {"uuid": "f442e34c-1ed3-4623-96a8-0485d7faa490", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31484", "type": "seen", "source": "https://bsky.app/profile/cyberalerts.bsky.social/post/3lluhfgnjdx2s", "content": "", "creation_timestamp": "2025-04-02T22:40:25.108371Z"} 2025-04-02T22:40:25.108371+00:00 https://vulnerability.circl.lu/sighting/df5648fc-2b3b-4a1e-b4e2-c1d05ad985d2/export 2026-07-19T07:44:54.488450+00:00 Automation user https://cvepremium.circl.lu/user/automation {"uuid": "df5648fc-2b3b-4a1e-b4e2-c1d05ad985d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31484", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10155", "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", "creation_timestamp": "2025-04-02T22:34:43.000000Z"} 2025-04-02T22:34:43+00:00 https://vulnerability.circl.lu/sighting/5648378e-2984-4bbd-ab87-986c5ba02610/export 2026-07-19T07:44:54.488746+00:00 Automation user https://cvepremium.circl.lu/user/automation {"uuid": "5648378e-2984-4bbd-ab87-986c5ba02610", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31484", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114270661068874157", "content": "", "creation_timestamp": "2025-04-02T22:11:54.290376Z"} 2025-04-02T22:11:54.290376+00:00 https://vulnerability.circl.lu/sighting/207d8033-1e72-4761-a5e5-48befe24faa8/export 2026-07-19T07:44:54.488994+00:00 Automation user https://cvepremium.circl.lu/user/automation {"uuid": "207d8033-1e72-4761-a5e5-48befe24faa8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31484", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114270661068874157", "content": "", "creation_timestamp": "2025-04-02T22:11:54.289319Z"} 2025-04-02T22:11:54.289319+00:00