<?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-09-29T17:12:05.374844+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/ghsa-vxpw-j846-p89q</id>
    <title>GHSA-vxpw-j846-p89q — undici WebSocket client vulnerable to denial of service via fragment count bypass</title>
    <updated>2026-09-29T17:12:05.388444+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: undici</p>
<p>## Impact</p>
<p>The undici WebSocket client enforces `maxPayloadSize` on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service.</p>
<p>Affected applications are those using the undici WebSocket client (`new WebSocket(...)`) or the `WebSocketStream` API that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint.</p>
<p>All releases starting at undici 6.17.0 are affected.</p>
<p>## Patches</p>
<p>Upgrade to undici v6.27.0, v7.28.0 or v8.5.0.</p>
<p>## Workarounds</p>
<p>No workaround is available. The fix must be applied through an upgrade.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-vxpw-j846-p89q"/>
  </entry>
</feed>
