<?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-12T10:04:46.837079+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/euvd-2026-232645</id>
    <title>EUVD-2026-232645</title>
    <updated>2026-10-12T10:04:46.839856+00:00</updated>
    <content>EUVD-2026-232645</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-232645"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-36078</id>
    <title>fkie_cve-2022-36078</title>
    <updated>2026-10-12T10:04:46.839884+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Binary provides encoding/decoding in Borsh and other formats. The vulnerability is a memory allocation vulnerability that can be exploited to allocate slices in memory with (arbitrary) excessive size value, which can either exhaust available memory or crash the whole program. When using `github.com/gagliardetto/binary` to parse unchecked (or wrong type of) data from untrusted sources of input (e.g. the blockchain) into slices, it's possible to allocate memory with excessive size. When `dec.Decode(&amp;val)` method is used to parse data into a structure that is or contains slices of values, the length of the slice was previously read directly from the data itself without any checks on the size of it, and then a slice was allocated. This could lead to an overflow and an allocation of memory with excessive size value. Users should upgrade to `v0.7.1` or higher. A workaround is not to rely on the `dec.Decode(&amp;val)` function to parse the data, but to use a custom `UnmarshalWithDecoder()` method that reads and checks the length of any slice.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-36078"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4p6f-m4f9-ch88</id>
    <title>GHSA-4p6f-m4f9-ch88 — Binary vulnerable to Slice Memory Allocation with Excessive Size Value</title>
    <updated>2026-10-12T10:04:46.839920+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/gagliardetto/binary</p>
<p>### Impact
&gt; _What kind of vulnerability is it? Who is impacted?_</p>
<p>The vulnerability is a memory allocation vulnerability that can be exploited to allocate slices in memory with (arbitrary) excessive size value, which can either exhaust available memory or crash the whole program.</p>
<p>When using `github.com/gagliardetto/binary` to parse unchecked (or wrong type of) data from untrusted sources of input (e.g. the blockchain) into slices, it's possible to allocate memory with excessive size.</p>
<p>When `dec.Decode(&amp;val)` method is used to parse data into a structure that is or contains slices of values, the length of the slice was previously read directly from the data itself without any checks on the size of it, and then a slice was allocated. This could lead to an overflow and an allocation of memory with excessive size value.</p>
<p>Example:</p>
<p>```go
package main</p>
<p>import (
	"github.com/gagliardetto/binary" // any version before v0.7.1 is vulnerable
	"log"
)</p>
<p>type MyStruct struct {
	Field1 []byte // field is a slice (could be a slice of any type)
}</p>
<p>func main() {
	// Let's assume that the data is coming from the blockchain:
	data := []byte{0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0a, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f, 0x10}
	
	var val MyStruct
	// - To determine the size of the val.Field1 slice, the decoder will read the length
	//   of the slice from the data itself without any checks on the size of it.
	//
	// - This could lead to an allocation of memory with excessive size value…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4p6f-m4f9-ch88"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-36078</id>
    <title>gsd-2022-36078</title>
    <updated>2026-10-12T10:04:46.839972+00:00</updated>
    <content>gsd-2022-36078</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-36078"/>
  </entry>
</feed>
