<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T15:28:09.873767+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/fkie_cve-2026-101914</id>
    <title>fkie_cve-2026-101914</title>
    <updated>2026-09-29T15:28:09.886775+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.1 and 1.14.1, the exact path (method name) matcher used by RBAC performs a prefix comparison instead of an equality comparison when case-insensitive matching is enabled. If one service method name prefixes another and the methods have different access rules, a request for the longer method can match the shorter method's rule and cause incorrect authorization. This issue is fixed in versions 1.13.1 and 1.14.1.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-101914"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-88h9-xgvx-hvf2</id>
    <title>GHSA-88h9-xgvx-hvf2 — @grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches</title>
    <updated>2026-09-29T15:28:09.886867+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @grpc/grpc-js-xds</p>
<p>### Impact
When using RBAC to apply authentication rules, the exact path (method name) matcher applies a prefix match instead of an exact match for case-insensitive matches. As a result, if a service has a method with a name that is a prefix of the name of a different method, and they have different access rules, and case-insensitive matching is used, this bug can cause improper authentication.</p>
<p>### Patches</p>
<p>This vulnerability is fixed in 1.13.1 and 1.14.1.</p>
<p>### Workarounds
This problem can be avoided by enabling case-sensitive path matching.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-88h9-xgvx-hvf2"/>
  </entry>
</feed>
