<?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-06T16:43:13.127736+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-330292</id>
    <title>EUVD-2026-330292</title>
    <updated>2026-10-06T16:43:13.131099+00:00</updated>
    <content>EUVD-2026-330292</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-330292"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48511</id>
    <title>fkie_cve-2026-48511</title>
    <updated>2026-10-06T16:43:13.131144+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7, ExpandoObjectFormatter.Deserialize populates System.Dynamic.ExpandoObject by calling IDictionary&lt;string, object&gt;.Add for each map entry. ExpandoObject internally maintains member names in array-like structures, so inserting many distinct keys can require repeated linear scans and array copies. For large attacker-controlled maps, this produces quadratic CPU and allocation behavior. The issue is especially surprising because ExpandoObjectResolver.Options is configured with MessagePackSecurity.UntrustedData, but collision-resistant dictionary comparers cannot protect ExpandoObject insertion internals. This vulnerability is fixed in 2.5.301 and 3.1.7.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-48511"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-2x83-8g95-xh59</id>
    <title>GHSA-2x83-8g95-xh59 — MessagePack-CSharp: ExpandoObject formatter can perform quadratic insertion work on untrusted maps</title>
    <updated>2026-10-06T16:43:13.131196+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> NuGet: MessagePack</p>
<p>## Summary</p>
<p>`ExpandoObjectFormatter.Deserialize` populates `System.Dynamic.ExpandoObject` by calling `IDictionary&lt;string, object&gt;.Add` for each map entry. `ExpandoObject` internally maintains member names in array-like structures, so inserting many distinct keys can require repeated linear scans and array copies.</p>
<p>For large attacker-controlled maps, this produces quadratic CPU and allocation behavior. The issue is especially surprising because `ExpandoObjectResolver.Options` is configured with `MessagePackSecurity.UntrustedData`, but collision-resistant dictionary comparers cannot protect `ExpandoObject` insertion internals.</p>
<p>## Impact</p>
<p>Applications are affected when they deserialize untrusted MessagePack maps into `ExpandoObject` using `ExpandoObjectResolver` or related resolver options.</p>
<p>A hostile payload containing many distinct keys can cause CPU exhaustion and allocation churn disproportionate to the input size. This can make a server unresponsive or exhaust memory under concurrent request load.</p>
<p>This is not a hash-collision attack against a configurable dictionary comparer. The super-linear behavior comes from `ExpandoObject`'s insertion model, so `MessagePackSecurity.UntrustedData` does not eliminate the cost.</p>
<p>## Affected components</p>
<p>- Package: `MessagePack`
- APIs: `ExpandoObjectFormatter.Deserialize`, `ExpandoObjectResolver`
- Data type: `System.Dynamic.ExpandoObject`
- Finding ID: `MESSAGEPACKCSHARP-102`</p>
<p>## Patches</p>
<p>Fixes are prepared and will be released in coor…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-2x83-8g95-xh59"/>
  </entry>
</feed>
