https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 21:56:44 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-12797 bdu:2025-12797 https://cve.radiocsirt.org/vuln/bdu:2025-12797 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1036 certfr-2025-avi-1036 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1036 https://cve.radiocsirt.org/vuln/cleanstart-2026-uk11362 <p><strong>Affected:</strong> CleanStart: gitness, CleanStart: gptscript</p> <p>CVE-2025-58058 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: gitness, CleanStart: gptscript</p> <p>CVE-2025-58058 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-uk11362 https://cve.radiocsirt.org/vuln/euvd-2026-251362 EUVD-2026-251362 https://cve.radiocsirt.org/vuln/euvd-2026-251362 https://cve.radiocsirt.org/vuln/fkie_cve-2025-58058 <p>xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn&#39;t include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.</p> <p>xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn&#39;t include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-58058 https://cve.radiocsirt.org/vuln/ghsa-jc7w-c686-c4v9 <p><strong>Affected:</strong> Go: github.com/ulikunitz/xz</p> <p>### Summary</p> <p>It is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn&#39;t include a magic number or has a checksum to detect such an issue according to the [specification](https://github.com/jljusten/LZMA-SDK/blob/master/DOC/lzma-specification.txt).</p> <p>Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done.</p> <p>### Mitigations</p> <p>The release v0.5.15 includes following mitigations:</p> <p>- The ReaderConfig DictCap field is now interpreted as a limit for the dictionary size. - The default is 2 Gigabytes - 1 byte (2^31-1 bytes). - Users can check with the [Reader.Header] method what the actual values are in their LZMA files and set a smaller limit using ReaderConfig. - The dictionary size will not exceed the larger of the file size and the minimum dictionary size. This is another measure to prevent huge memory allocations for the dictionary. - The code supports stream sizes only up to a pebibyte (1024^5).</p> <p>Note that the original v0.5.14 version had a compiler error for 32 bit platforms, which has been fixed by v0.5.15.</p> <p>### Methods affected</p> <p>Only software that uses [lzma.NewReader](https://pkg.go.dev/github.com/ulikunitz/xz/lzma#NewReader) or [lzma.ReaderConfig.NewReader](http…</p> <p><strong>Affected:</strong> Go: github.com/ulikunitz/xz</p> <p>### Summary</p> <p>It is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn&#39;t include a magic number or has a checksum to detect such an issue according to the [specification](https://github.com/jljusten/LZMA-SDK/blob/master/DOC/lzma-specification.txt).</p> <p>Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done.</p> <p>### Mitigations</p> <p>The release v0.5.15 includes following mitigations:</p> <p>- The ReaderConfig DictCap field is now interpreted as a limit for the dictionary size. - The default is 2 Gigabytes - 1 byte (2^31-1 bytes). - Users can check with the [Reader.Header] method what the actual values are in their LZMA files and set a smaller limit using ReaderConfig. - The dictionary size will not exceed the larger of the file size and the minimum dictionary size. This is another measure to prevent huge memory allocations for the dictionary. - The code supports stream sizes only up to a pebibyte (1024^5).</p> <p>Note that the original v0.5.14 version had a compiler error for 32 bit platforms, which has been fixed by v0.5.15.</p> <p>### Methods affected</p> <p>Only software that uses [lzma.NewReader](https://pkg.go.dev/github.com/ulikunitz/xz/lzma#NewReader) or [lzma.ReaderConfig.NewReader](http…</p> https://cve.radiocsirt.org/vuln/ghsa-jc7w-c686-c4v9 https://cve.radiocsirt.org/vuln/msrc_cve-2025-58058 msrc_CVE-2025-58058 https://cve.radiocsirt.org/vuln/msrc_cve-2025-58058 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15503-1 <p>tailscale-1.86.5-1.1 on GA media</p> <p>tailscale-1.86.5-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15503-1 https://cve.radiocsirt.org/vuln/rhsa-2026:26254 <p>github.com/ulikunitz/xz: github.com/ulikunitz/xz leaks memory github.com/open-telemetry/opentelemetry-go: OpenTelemetry-Go: Arbitrary code execution via PATH hijacking on BSD/Solaris</p> <p>github.com/ulikunitz/xz: github.com/ulikunitz/xz leaks memory github.com/open-telemetry/opentelemetry-go: OpenTelemetry-Go: Arbitrary code execution via PATH hijacking on BSD/Solaris</p> https://cve.radiocsirt.org/vuln/rhsa-2026:26254 https://cve.radiocsirt.org/vuln/suse-su-2025:03448-1 <p>Security update for warewulf4</p> <p>Security update for warewulf4</p> https://cve.radiocsirt.org/vuln/suse-su-2025:03448-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-58058 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: golang-github-ulikunitz-xz, Ubuntu:22.04:LTS: golang-github-ulikunitz-xz, Ubuntu:24.04:LTS: golang-github-ulikunitz-xz, Ubuntu:25.10: golang-github-ulikunitz-xz, Ubuntu:26.04:LTS: golang-github-ulikunitz-xz</p> <p>xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn&#39;t include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: golang-github-ulikunitz-xz, Ubuntu:22.04:LTS: golang-github-ulikunitz-xz, Ubuntu:24.04:LTS: golang-github-ulikunitz-xz, Ubuntu:25.10: golang-github-ulikunitz-xz, Ubuntu:26.04:LTS: golang-github-ulikunitz-xz</p> <p>xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn&#39;t include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-58058