https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sat, 02 May 2026 13:30:22 +0000 https://db.gcve.eu/sighting/7ce3efd9-83d0-46f2-ba31-2fbc61578578/export {"uuid": "7ce3efd9-83d0-46f2-ba31-2fbc61578578", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-50178", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/19467", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-50178\n\ud83d\udd25 CVSS Score: 6.6 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U)\n\ud83d\udd39 Description: GitForge.jl is a unified interface for interacting with Git \"forges.\" Versions prior to 0.4.3 lack input validation for user provided values in certain functions. In the `GitForge.get_repo` function for GitHub, the user can provide any string for the owner and repo fields. These inputs are not validated or safely encoded and are sent directly to the server. This means a user can add path traversal patterns like `../` in the input to access any other endpoints on api.github.com that were not intended. Version 0.4.3 contains a patch for the issue. No known workarounds are available.\n\ud83d\udccf Published: 2025-06-25T15:12:24.751Z\n\ud83d\udccf Modified: 2025-06-25T15:20:43.040Z\n\ud83d\udd17 References:\n1. https://github.com/JuliaWeb/GitForge.jl/security/advisories/GHSA-g2xx-229f-3qjm\n2. https://github.com/JuliaWeb/GitForge.jl/pull/50", "creation_timestamp": "2025-06-25T15:52:13.000000Z"} {"uuid": "7ce3efd9-83d0-46f2-ba31-2fbc61578578", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-50178", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/19467", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-50178\n\ud83d\udd25 CVSS Score: 6.6 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U)\n\ud83d\udd39 Description: GitForge.jl is a unified interface for interacting with Git \"forges.\" Versions prior to 0.4.3 lack input validation for user provided values in certain functions. In the `GitForge.get_repo` function for GitHub, the user can provide any string for the owner and repo fields. These inputs are not validated or safely encoded and are sent directly to the server. This means a user can add path traversal patterns like `../` in the input to access any other endpoints on api.github.com that were not intended. Version 0.4.3 contains a patch for the issue. No known workarounds are available.\n\ud83d\udccf Published: 2025-06-25T15:12:24.751Z\n\ud83d\udccf Modified: 2025-06-25T15:20:43.040Z\n\ud83d\udd17 References:\n1. https://github.com/JuliaWeb/GitForge.jl/security/advisories/GHSA-g2xx-229f-3qjm\n2. https://github.com/JuliaWeb/GitForge.jl/pull/50", "creation_timestamp": "2025-06-25T15:52:13.000000Z"} https://db.gcve.eu/sighting/7ce3efd9-83d0-46f2-ba31-2fbc61578578/export Wed, 25 Jun 2025 15:52:13 +0000