# CVE-2026-101916: @grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized

> Attackers can bypass authentication in gRPC JavaScript applications by presenting unauthorized certificates when client certificate requirements are disabled.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** CLEANSTART-2026-AS30225, CLEANSTART-2026-GT88240, CLEANSTART-2026-HQ75468, CLEANSTART-2026-LD22017, ECHO-bc2f-c80e-b44d, GHSA-m9gg-hp2v-232j, MINI-2g8f-38xq-2gg8, MINI-439f-q38w-2j8x, MINI-444w-cjv8-r5mw, MINI-4mg7-wfg3-877r, MINI-5hhr-jfjp-x3jf, MINI-5hq4-54jm-73vv, MINI-7c44-chvj-q6fv, MINI-7g9j-g343-c24c, MINI-f8w9-6g9h-rqh3, MINI-gccp-69mh-w9jj, MINI-mqx3-j399-6qcj, MINI-q3qx-5cj8-7g2m, MINI-q98p-m76r-6rh6, MINI-qwvv-99vw-4532, MINI-w2j5-283q-23j9, ROOT-APP-NPM-CVE-2026-101916

## What is CVE-2026-101916?

CVE-2026-101916 is a high-severity authentication bypass vulnerability in grpc-node, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

@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, getAuthContext does not distinguish authorized from unauthorized peer certificates when server credentials set requireClientCertificate to false. When applications use the returned authentication context, they can treat an unauthorized certificate as authorized, causing improper authentication. @grpc/grpc-js-xds can reach this condition when RBAC authentication is enabled in affected configurations. This issue is fixed in version 1.14.5 and 1.13.6.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-101916?

4 open source packages ship an affected version, including @grpc/grpc-js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@grpc/grpc-js` | npm | All versions | 1.13.6 |
| `@grpc/grpc-js` | npm | All versions | 1.13.6 |
| `@grpc/grpc-js` | npm | From 1.14.0 | 1.14.5 |
| `@grpc/grpc-js` | npm | From 1.14.0 | 1.14.5 |

## How do I fix CVE-2026-101916?

Upgrade @grpc/grpc-js to a fixed version for your release line: 1.13.6 or 1.14.5.

## Is CVE-2026-101916 being exploited?

There is no known exploitation of CVE-2026-101916 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101916 and fix it if it is affected.

What it is: CVE-2026-101916 is a high-severity authentication bypass vulnerability in grpc-node, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101916 in the wild and no public exploit code.

Affected packages and fixed versions:
- @grpc/grpc-js (npm): affected all versions; fixed in 1.13.6
- @grpc/grpc-js (npm): affected all versions; fixed in 1.13.6
- @grpc/grpc-js (npm): affected from 1.14.0; fixed in 1.14.5
- @grpc/grpc-js (npm): affected from 1.14.0; fixed in 1.14.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101916/ (Markdown: https://insights.sbomify.com/CVE-2026-101916/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101916
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101916
- OSV: https://osv.dev/vulnerability/CVE-2026-101916

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101916/
Summaries are generated and may contain mistakes; the official description above is the record.