CVE-2026-48068
HIGH@grpc/grps-js: A malformed request can cause a server crash
Blast Radius
@grpc/grpc-js📦@grpc/grpc-js📦@grpc/grpc-js📦@grpc/grpc-js📦@grpc/grpc-js📦@grpc/grpc-jsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4, an invalid incoming HTTP/2 stream initiation can cause a server process created using @grpc/grpc-js to crash. This issue is fixed in versions 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @grpc/grpc-js | all versions | 1.9.16 |
| 📦npm | @grpc/grpc-js | ≥ 1.10.0&&< 1.10.12 | 1.10.12 |
| 📦npm | @grpc/grpc-js | ≥ 1.11.0&&< 1.11.4 | 1.11.4 |
| 📦npm | @grpc/grpc-js | ≥ 1.12.0&&< 1.12.7 | 1.12.7 |
| 📦npm | @grpc/grpc-js | ≥ 1.13.0&&< 1.13.5 | 1.13.5 |
| 📦npm | @grpc/grpc-js | ≥ 1.14.0&&< 1.14.4 | 1.14.4 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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 CVE-2026-48068 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2026-48068 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 CVE-2026-48068. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-48068 in your dependencies?
O3 detects CVE-2026-48068 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.