Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-5375-pq7m-f5r2

HIGH

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

Also known asCVE-2026-48068
Published
Jun 11, 2026
Updated
Jun 12, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk46th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@grpc/grpc-jsnpm
42.0Mdownloads / week

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.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
📦npm@grpc/grpc-jsall versions1.9.16
📦npm@grpc/grpc-js1.10.0&&< 1.10.121.10.12
📦npm@grpc/grpc-js1.11.0&&< 1.11.41.11.4
📦npm@grpc/grpc-js1.12.0&&< 1.12.71.12.7
📦npm@grpc/grpc-js1.13.0&&< 1.13.51.13.5
📦npm@grpc/grpc-js1.14.0&&< 1.14.41.14.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @grpc/grpc-js. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update @grpc/grpc-js to 1.9.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5375-pq7m-f5r2 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5375-pq7m-f5r2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5375-pq7m-f5r2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.
O3 Security · Impact-Aware SCA

Is GHSA-5375-pq7m-f5r2 in your dependencies?

O3 detects GHSA-5375-pq7m-f5r2 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.