<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 16:34:28 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-245849</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-245849</link>
      <description>EUVD-2026-245849</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-245849</guid>
    </item>
    <item>
      <title>fkie_cve-2025-50178</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-50178</link>
      <description>&lt;p&gt;GitForge.jl is a unified interface for interacting with Git &amp;#34;forges.&amp;#34; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitForge.jl is a unified interface for interacting with Git &amp;#34;forges.&amp;#34; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-50178</guid>
    </item>
  </channel>
</rss>
