Skip to content

@grpc/grpc-js: A malformed request can cause a server crash

High severity GitHub Reviewed Published May 20, 2026 in grpc/grpc-node • Updated Jun 11, 2026

Package

npm @grpc/grpc-js (npm)

Affected versions

< 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

Patched versions

1.9.16
1.10.12
1.11.4
1.12.7
1.13.5
1.14.4

Description

Impact

An invalid incoming HTTP/2 stream initiation can cause a server process to crash. This affects all servers created using @grpc/grpc-js.

Patches

The following version have fixes for this vulnerability:

  • 1.9.16
  • 1.10.12
  • 1.11.4
  • 1.12.7
  • 1.13.5
  • 1.14.4

Workarounds

There is no workaround.

References

@murgatroid99 murgatroid99 published to grpc/grpc-node May 20, 2026
Published to the GitHub Advisory Database Jun 11, 2026
Reviewed Jun 11, 2026
Last updated Jun 11, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(17th percentile)

Weaknesses

Uncaught Exception

An exception is thrown from a function, but it is not caught. Learn more on MITRE.

CVE ID

CVE-2026-48068

GHSA ID

GHSA-5375-pq7m-f5r2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.