<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-30T23:16:39.470295+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-116583</id>
    <title>fkie_cve-2026-116583</title>
    <updated>2026-10-30T23:16:39.967008+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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'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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-116583"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-f86p-h4j2-7qgj</id>
    <title>GHSA-f86p-h4j2-7qgj — Seroval: Code injection through a typed array's own constructor property</title>
    <updated>2026-10-30T23:16:39.967137+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: seroval</p>
<p>### Summary</p>
<p>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.</p>
<p>### Details</p>
<p>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's real type.</p>
<p>These functions are affected:</p>
<p>- `serialize`, `serializeAsync`
- `crossSerialize`, `crossSerializeAsync`, `crossSerializeStream`
- the `Serializer` class
- `compileJSON`</p>
<p>`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.</p>
<p>### Impact</p>
<p>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.</p>
<p>### Patches</p>
<p>Fixed in 1.6.11. The constructor name now comes from the array's internal type, which properties on the…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-f86p-h4j2-7qgj"/>
  </entry>
</feed>
