<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T17:27:38.880584+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-58183</id>
    <title>CVE-2025-58183 — Unbounded allocation when parsing GNU sparse map in archive/tar</title>
    <updated>2026-10-05T17:27:38.909630+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go standard library archive/tar</p>
<p>tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When reading from a compressed source, a small compressed input can result in large allocations.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-58183"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-2c4m-59x9-fr2g</id>
    <title>GHSA-2c4m-59x9-fr2g — Gin Web Framework does not properly sanitize filename parameter of Context.FileAttachment function</title>
    <updated>2026-10-05T17:27:38.909701+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/gin-gonic/gin</p>
<p>The filename parameter of the Context.FileAttachment function is not properly sanitized. A maliciously crafted filename can cause the Content-Disposition header to be sent with an unexpected filename value or otherwise modify the Content-Disposition header. For example, a filename of "setup.bat&amp;quot;;x=.txt" will be sent as a file named "setup.bat".</p>
<p>If the FileAttachment function is called with names provided by an untrusted source, this may permit an attacker to cause a file to be served with a name different than provided. Maliciously crafted attachment file name can modify the Content-Disposition header.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-2c4m-59x9-fr2g"/>
  </entry>
</feed>
