https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Fri, 08 May 2026 12:18:03 +0000 https://vulnerability.circl.lu/sighting/cc97990c-21af-4ca9-9930-f4f074374bd6/export {"uuid": "cc97990c-21af-4ca9-9930-f4f074374bd6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31130", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10475", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-31130\n\ud83d\udd25 CVSS Score: 6.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N)\n\ud83d\udd39 Description: gitoxide is an implementation of git written in Rust. Before 0.42.0, gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks. gitoxide uses the sha1_smol or sha1 crate, both of which implement standard SHA-1 without any mitigations for collision attacks. This means that two distinct Git objects with colliding SHA-1 hashes would break the Git object model and integrity checks when used with gitoxide. This vulnerability is fixed in 0.42.0.\n\ud83d\udccf Published: 2025-04-04T14:41:56.355Z\n\ud83d\udccf Modified: 2025-04-04T14:51:51.207Z\n\ud83d\udd17 References:\n1. https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-2frx-2596-x5r6\n2. https://github.com/GitoxideLabs/gitoxide/commit/4660f7a6f71873311f68f170b0f1f6659a02829d", "creation_timestamp": "2025-04-04T15:37:01.000000Z"} {"uuid": "cc97990c-21af-4ca9-9930-f4f074374bd6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31130", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10475", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-31130\n\ud83d\udd25 CVSS Score: 6.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N)\n\ud83d\udd39 Description: gitoxide is an implementation of git written in Rust. Before 0.42.0, gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks. gitoxide uses the sha1_smol or sha1 crate, both of which implement standard SHA-1 without any mitigations for collision attacks. This means that two distinct Git objects with colliding SHA-1 hashes would break the Git object model and integrity checks when used with gitoxide. This vulnerability is fixed in 0.42.0.\n\ud83d\udccf Published: 2025-04-04T14:41:56.355Z\n\ud83d\udccf Modified: 2025-04-04T14:51:51.207Z\n\ud83d\udd17 References:\n1. https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-2frx-2596-x5r6\n2. https://github.com/GitoxideLabs/gitoxide/commit/4660f7a6f71873311f68f170b0f1f6659a02829d", "creation_timestamp": "2025-04-04T15:37:01.000000Z"} https://vulnerability.circl.lu/sighting/cc97990c-21af-4ca9-9930-f4f074374bd6/export Fri, 04 Apr 2025 15:37:01 +0000 https://vulnerability.circl.lu/sighting/d837317f-ab74-4944-92fa-19523a232d19/export {"uuid": "d837317f-ab74-4944-92fa-19523a232d19", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31130", "type": "seen", "source": "https://t.me/cvedetector/22129", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-31130 - Gitoxide SHA-1 Hash Collision Attack Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-31130 \nPublished : April 4, 2025, 3:15 p.m. | 41\u00a0minutes ago \nDescription : gitoxide is an implementation of git written in Rust. Before 0.42.0, gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks. gitoxide uses the sha1_smol or sha1 crate, both of which implement standard SHA-1 without any mitigations for collision attacks. This means that two distinct Git objects with colliding SHA-1 hashes would break the Git object model and integrity checks when used with gitoxide. This vulnerability is fixed in 0.42.0. \nSeverity: 6.8 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"04 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-04T18:01:13.000000Z"} {"uuid": "d837317f-ab74-4944-92fa-19523a232d19", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31130", "type": "seen", "source": "https://t.me/cvedetector/22129", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-31130 - Gitoxide SHA-1 Hash Collision Attack Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-31130 \nPublished : April 4, 2025, 3:15 p.m. | 41\u00a0minutes ago \nDescription : gitoxide is an implementation of git written in Rust. Before 0.42.0, gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks. gitoxide uses the sha1_smol or sha1 crate, both of which implement standard SHA-1 without any mitigations for collision attacks. This means that two distinct Git objects with colliding SHA-1 hashes would break the Git object model and integrity checks when used with gitoxide. This vulnerability is fixed in 0.42.0. \nSeverity: 6.8 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"04 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-04T18:01:13.000000Z"} https://vulnerability.circl.lu/sighting/d837317f-ab74-4944-92fa-19523a232d19/export Fri, 04 Apr 2025 18:01:13 +0000