<?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>Wed, 21 Oct 2026 23:39:01 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-221514</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-221514</link>
      <description>EUVD-2026-221514</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-221514</guid>
    </item>
    <item>
      <title>fkie_cve-2022-23535</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-23535</link>
      <description>&lt;p&gt;LiteDB is a small, fast and lightweight .NET NoSQL embedded database. Versions prior to 5.0.13 are subject to Deserialization of Untrusted Data. LiteDB uses a special field in JSON documents to cast different types from `BsonDocument` to POCO classes. When instances of an object are not the same of class, `BsonMapper` use a special field `_type` string info with full class name with assembly to be loaded and fit into your model. If your end-user can send to your app a plain JSON string, deserialization can load an unsafe  object to fit into your model. This issue is patched in version 5.0.13 with some basic fixes to avoid this, but is not 100% guaranteed when using `Object` type. The next major version will contain an allow-list to select what kind of Assembly can be loaded. Workarounds are detailed in the vendor advisory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;LiteDB is a small, fast and lightweight .NET NoSQL embedded database. Versions prior to 5.0.13 are subject to Deserialization of Untrusted Data. LiteDB uses a special field in JSON documents to cast different types from `BsonDocument` to POCO classes. When instances of an object are not the same of class, `BsonMapper` use a special field `_type` string info with full class name with assembly to be loaded and fit into your model. If your end-user can send to your app a plain JSON string, deserialization can load an unsafe  object to fit into your model. This issue is patched in version 5.0.13 with some basic fixes to avoid this, but is not 100% guaranteed when using `Object` type. The next major version will contain an allow-list to select what kind of Assembly can be loaded. Workarounds are detailed in the vendor advisory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-23535</guid>
    </item>
    <item>
      <title>GHSA-3x49-g6rc-c284 — LiteDB may deserialize bad JSON on object type using _type</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3x49-g6rc-c284</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NuGet: LiteDB&lt;/p&gt;
&lt;p&gt;### Impact
LiteDB use a special field in JSON documents to cast diferent types from `BsonDocument` do POCO classes. When instance of an object are not the same of class, `BsonMapper` use a special field `_type` string info with full class name with assembly to be loaded and fit in your model.
If your end-user can send to your app a plain JSON string, deserialization can load an unsafe  object to fit in your model.&lt;/p&gt;
&lt;p&gt;### Patches
Version &amp;gt;= 5.0.13 add some basic fixes to avoid this, but is not 100% guaranteed when using `Object` type
Next major version will contains a allow-list to select what king of Assembly can be loaded&lt;/p&gt;
&lt;p&gt;### Workarounds
- Avoid users send to your app a JSON string to be direct insert/update into database
- Avoid use classes with `Object` type - try use an interface when possible&lt;/p&gt;
&lt;p&gt;If your app send a plain JSON string to be insert/update into database, prefer this:
```
// Bad
public class Customer {
    public int Id { get; set; }
    public string Name { get; set; }
    public Object AnyData { get; set; } // &amp;lt;= Avoid use `Object` base type
}&lt;/p&gt;
&lt;p&gt;// Good
public class Customer {
    public int Id { get; set; }
    public string Name { get; set; }
    public IDictionary&amp;lt;string, string&amp;gt; AnyData { get; set; } // Will accept only key/value strings
}&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;### References
See this workaround fix on this commit:&lt;/p&gt;
&lt;p&gt;https://github.com/mbdavid/LiteDB/commit/4382ff4dd0dd8b8b16a4e37dfd29727c5f70f93f&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NuGet: LiteDB&lt;/p&gt;
&lt;p&gt;### Impact
LiteDB use a special field in JSON documents to cast diferent types from `BsonDocument` do POCO classes. When instance of an object are not the same of class, `BsonMapper` use a special field `_type` string info with full class name with assembly to be loaded and fit in your model.
If your end-user can send to your app a plain JSON string, deserialization can load an unsafe  object to fit in your model.&lt;/p&gt;
&lt;p&gt;### Patches
Version &amp;gt;= 5.0.13 add some basic fixes to avoid this, but is not 100% guaranteed when using `Object` type
Next major version will contains a allow-list to select what king of Assembly can be loaded&lt;/p&gt;
&lt;p&gt;### Workarounds
- Avoid users send to your app a JSON string to be direct insert/update into database
- Avoid use classes with `Object` type - try use an interface when possible&lt;/p&gt;
&lt;p&gt;If your app send a plain JSON string to be insert/update into database, prefer this:
```
// Bad
public class Customer {
    public int Id { get; set; }
    public string Name { get; set; }
    public Object AnyData { get; set; } // &amp;lt;= Avoid use `Object` base type
}&lt;/p&gt;
&lt;p&gt;// Good
public class Customer {
    public int Id { get; set; }
    public string Name { get; set; }
    public IDictionary&amp;lt;string, string&amp;gt; AnyData { get; set; } // Will accept only key/value strings
}&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;### References
See this workaround fix on this commit:&lt;/p&gt;
&lt;p&gt;https://github.com/mbdavid/LiteDB/commit/4382ff4dd0dd8b8b16a4e37dfd29727c5f70f93f&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3x49-g6rc-c284</guid>
    </item>
    <item>
      <title>gsd-2022-23535</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-23535</link>
      <description>gsd-2022-23535</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-23535</guid>
    </item>
  </channel>
</rss>
