What is CVE-2026-101914?

CVE-2026-101914 is a medium-severity incorrect authorization vulnerability in @grpc/grpc-js-xds (npm), affecting versions < 1.13.1. It is fixed in 1.13.1, 1.14.1. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is CVE-2026-101914?

CVE-2026-101914 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @grpc/grpc-js-xds are affected by CVE-2026-101914?

@grpc/grpc-js-xds (npm) versions < 1.13.1 is affected.

Is there a fix for CVE-2026-101914?

Yes. CVE-2026-101914 is fixed in 1.13.1, 1.14.1. Upgrade to this version or later.

Is CVE-2026-101914 exploitable, and should I be worried?

Whether CVE-2026-101914 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-101914 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-101914?

Upgrade: @grpc/grpc-js-xds to 1.13.1 or later, @grpc/grpc-js-xds to 1.14.1 or later.

CVE-2026-101914 in @grpc/grpc-js-xds

Q: How severe is CVE-2026-101914?

CVE-2026-101914 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @grpc/grpc-js-xds are affected by CVE-2026-101914?

@grpc/grpc-js-xds (npm) versions < 1.13.1 is affected.

Q: Is there a fix for CVE-2026-101914?

Yes. CVE-2026-101914 is fixed in 1.13.1, 1.14.1. Upgrade to this version or later.

Q: Is CVE-2026-101914 exploitable, and should I be worried?

Whether CVE-2026-101914 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-101914 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-101914?

Upgrade: @grpc/grpc-js-xds to 1.13.1 or later, @grpc/grpc-js-xds to 1.14.1 or later.

Summary

@grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches

Workarounds

This problem can be avoided by enabling case-sensitive path matching.

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-101914 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.13.1, 1.14.1); upgrading removes the vulnerable code path.

Affected versions

@grpc/grpc-js-xds (< 1.13.1) @grpc/grpc-js-xds (= 1.14.0)

Security releases

@grpc/grpc-js-xds → 1.13.1 (npm) @grpc/grpc-js-xds → 1.14.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This vulnerability is fixed in 1.13.1 and 1.14.1.

Frequently Asked Questions

What is CVE-2026-101914? CVE-2026-101914 is a medium-severity incorrect authorization vulnerability in @grpc/grpc-js-xds (npm), affecting versions < 1.13.1. It is fixed in 1.13.1, 1.14.1. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
How severe is CVE-2026-101914? CVE-2026-101914 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @grpc/grpc-js-xds are affected by CVE-2026-101914? @grpc/grpc-js-xds (npm) versions < 1.13.1 is affected.
Is there a fix for CVE-2026-101914? Yes. CVE-2026-101914 is fixed in 1.13.1, 1.14.1. Upgrade to this version or later.
Is CVE-2026-101914 exploitable, and should I be worried? Whether CVE-2026-101914 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-101914 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-101914?
- Upgrade @grpc/grpc-js-xds to 1.13.1 or later
- Upgrade @grpc/grpc-js-xds to 1.14.1 or later