<?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-01T15:54:33.446671+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-101915</id>
    <title>fkie_cve-2026-101915</title>
    <updated>2026-10-01T15:54:33.457364+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.13.6 and 1.14.5, when an application method handler throws an uncaught error, the server includes its error message in the status message sent to the client. The thrown error message is transmitted to the client, causing sensitive information disclosure when the message contains sensitive data. This issue is fixed in versions 1.13.6 and 1.14.5.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-101915"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-f596-whhp-79r4</id>
    <title>GHSA-f596-whhp-79r4 — @grpc/grpc-js: The server transmits some error messages thrown by method handlers to the client in status messages</title>
    <updated>2026-10-01T15:54:33.457427+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @grpc/grpc-js</p>
<p>### Impact
If an application method handler crashes, the error message is included in the status message sent to the client. This can leak to the client any sensitive data that may be included in the error message. This impacts anyone using `@grpc/grpc-js` to run servers.</p>
<p>### Patches
This vulnerability is fixed in 1.13.6 and 1.14.5.</p>
<p>### Workarounds
This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-f596-whhp-79r4"/>
  </entry>
</feed>
