CVE-2026-48068: @grpc/grpc-js Server Crash Due to Malformed HTTP/2 Request

@grpc/grpc-js Updated 11 Jun 2026

Summary

11/06/2026

Disclosed on

CVE-2026-48068

CVE

Yes i

Fix available

High

Severity

7.5

CVSS Score

CVE-2026-48068: @grpc/grpc-js: A malformed request can cause a server crash. Affects @grpc/grpc-js across 6 version ranges.

< 1.9.16 >= 1.10.0, < 1.10.12 >= 1.11.0, < 1.11.4 >= 1.12.0, < 1.12.7 >= 1.13.0, < 1.13.5 >= 1.14.0, < 1.14.4

Fixed in 6 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

The @grpc/grpc-js package is a popular library for implementing gRPC in Node.js applications. It provides a high-performance, language-agnostic framework for remote procedure calls, enabling efficient communication between services. However, a vulnerability has been identified that can lead to server crashes when handling malformed HTTP/2 requests.

Vulnerability Detail

An invalid incoming HTTP/2 stream initiation can cause a server process to crash. This vulnerability affects all servers created using the @grpc/grpc-js package. The issue arises from the way the library processes incoming requests, leading to potential denial of service if exploited. The severity of this vulnerability is rated high, with a CVSS score of 7.5, indicating significant risk to applications relying on this package.

How To Fix

Latest published version: 1.14.6 as of 23 Oct 2026

npm install @grpc/grpc-js@1.14.6

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

< 1.9.16 1.9.16
```
npm install @grpc/grpc-js@1.9.16
```
>= 1.10.0, < 1.10.12 1.10.12
```
npm install @grpc/grpc-js@1.10.12
```
>= 1.11.0, < 1.11.4 1.11.4
```
npm install @grpc/grpc-js@1.11.4
```
>= 1.12.0, < 1.12.7 1.12.7
```
npm install @grpc/grpc-js@1.12.7
```
>= 1.13.0, < 1.13.5 1.13.5
```
npm install @grpc/grpc-js@1.13.5
```
>= 1.14.0, < 1.14.4 1.14.4
```
npm install @grpc/grpc-js@1.14.4
```

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is currently no workaround available for this vulnerability. The only effective solution is to update to a patched version of the package.

Conclusion

In summary, CVE-2026-48068 is a critical vulnerability in the @grpc/grpc-js package that can lead to server crashes due to malformed HTTP/2 requests. It is essential for developers to update to the patched versions to mitigate the risk of denial of service in their applications.

See every vulnerability recorded for @grpc/grpc-js →

FAQ

What is CVE-2026-48068?

CVE-2026-48068 is a vulnerability in the @grpc/grpc-js package that can cause a server crash due to malformed HTTP/2 requests.

How does this vulnerability affect my application?

If your application uses the @grpc/grpc-js package, it may be susceptible to crashes when handling malformed HTTP/2 requests, leading to potential downtime.

What should I do if I cannot update the package immediately?

Currently, there are no workarounds for this vulnerability. It is recommended to prioritize updating the package to a patched version as soon as possible.

How can I check if my application is affected?

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.