<?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://db.gcve.eu</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>Fri, 30 Oct 2026 23:16:39 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-116583</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-116583</link>
      <description>&lt;p&gt;Seroval facilitates JavaScript value stringification, including complex structures beyond JSON.stringify capabilities. From 1.6.0 until 1.6.11, the JavaScript-output APIs derive a typed array&amp;#39;s constructor name from a property on the value that can be replaced by an own constructor property. When application code copies untrusted properties onto a typed array and then passes it to serialize, serializeAsync, crossSerialize, crossSerializeAsync, crossSerializeStream, Serializer, or compileJSON, the attacker-controlled name is written as executable JavaScript and can run in the page receiving the output. This issue is fixed in version 1.6.11.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Seroval facilitates JavaScript value stringification, including complex structures beyond JSON.stringify capabilities. From 1.6.0 until 1.6.11, the JavaScript-output APIs derive a typed array&amp;#39;s constructor name from a property on the value that can be replaced by an own constructor property. When application code copies untrusted properties onto a typed array and then passes it to serialize, serializeAsync, crossSerialize, crossSerializeAsync, crossSerializeStream, Serializer, or compileJSON, the attacker-controlled name is written as executable JavaScript and can run in the page receiving the output. This issue is fixed in version 1.6.11.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-116583</guid>
    </item>
    <item>
      <title>GHSA-f86p-h4j2-7qgj — Seroval: Code injection through a typed array's own constructor property</title>
      <link>https://db.gcve.eu/vuln/ghsa-f86p-h4j2-7qgj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: seroval&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;seroval writes a typed array as a call to its constructor. In affected versions, the constructor name in the output is read from a property that data on the value can replace, and it is written without checks. A typed array that received properties from untrusted data can then put arbitrary code into the serialized output.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Version 1.6.0 changed how seroval finds the class of an object, so that objects with their own `constructor` property serialize correctly. Typed arrays still took the constructor name from the value itself, so the name could come from the untrusted property instead of the array&amp;#39;s real type.&lt;/p&gt;
&lt;p&gt;These functions are affected:&lt;/p&gt;
&lt;p&gt;- `serialize`, `serializeAsync`
- `crossSerialize`, `crossSerializeAsync`, `crossSerializeStream`
- the `Serializer` class
- `compileJSON`&lt;/p&gt;
&lt;p&gt;`fromJSON` and `fromCrossJSON` are not affected: they only accept the names of the built-in typed arrays. With the `compactArrayBufferViews` option, the same lookup throws a `TypeError` instead of writing code.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An application is affected only when it serializes a typed array that has an own `constructor` property set from untrusted data. That requires code that copies properties from untrusted objects onto a typed array. This is unusual, so the severity is rated Low, even though the result is script execution in the page that receives the output.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in 1.6.11. The constructor name now comes from the array&amp;#39;s internal type, which properties on the…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: seroval&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;seroval writes a typed array as a call to its constructor. In affected versions, the constructor name in the output is read from a property that data on the value can replace, and it is written without checks. A typed array that received properties from untrusted data can then put arbitrary code into the serialized output.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Version 1.6.0 changed how seroval finds the class of an object, so that objects with their own `constructor` property serialize correctly. Typed arrays still took the constructor name from the value itself, so the name could come from the untrusted property instead of the array&amp;#39;s real type.&lt;/p&gt;
&lt;p&gt;These functions are affected:&lt;/p&gt;
&lt;p&gt;- `serialize`, `serializeAsync`
- `crossSerialize`, `crossSerializeAsync`, `crossSerializeStream`
- the `Serializer` class
- `compileJSON`&lt;/p&gt;
&lt;p&gt;`fromJSON` and `fromCrossJSON` are not affected: they only accept the names of the built-in typed arrays. With the `compactArrayBufferViews` option, the same lookup throws a `TypeError` instead of writing code.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An application is affected only when it serializes a typed array that has an own `constructor` property set from untrusted data. That requires code that copies properties from untrusted objects onto a typed array. This is unusual, so the severity is rated Low, even though the result is script execution in the page that receives the output.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in 1.6.11. The constructor name now comes from the array&amp;#39;s internal type, which properties on the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-f86p-h4j2-7qgj</guid>
    </item>
  </channel>
</rss>
