Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2026-48069 — @grpc/grpc-js

HIGHFix: grpc/grpc-node@2375ead

CVE-2026-48069 is a high-severity (CVSS 7.5) CWE-248 vulnerability in @grpc/grpc-js. A fix is available for @grpc/grpc-js — see the affected versions and patch details below.

@grpc/grps-js: An incoming malformed compressed message can cause a client or server crash

Also known asGHSA-99f4-grh7-6pcq
Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-48069.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk
0.12%0.54%0.96%1.38%0.6%0.9%0.9%0.9%Aug 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-48069 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

6 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@grpc/grpc-jsnpm
60.2Mdownloads / week

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 compressed message can cause a client or server process that uses @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

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
📦npm@grpc/grpc-jsall versions1.9.16npm install @grpc/grpc-js@1.9.16
📦npm@grpc/grpc-js≥ 1.10.0&&< 1.10.121.10.12npm install @grpc/grpc-js@1.10.12
📦npm@grpc/grpc-js≥ 1.11.0&&< 1.11.41.11.4npm install @grpc/grpc-js@1.11.4
📦npm@grpc/grpc-js≥ 1.12.0&&< 1.12.71.12.7npm install @grpc/grpc-js@1.12.7
📦npm@grpc/grpc-js≥ 1.13.0&&< 1.13.51.13.5npm install @grpc/grpc-js@1.13.5
📦npm@grpc/grpc-js≥ 1.14.0&&< 1.14.41.14.4npm install @grpc/grpc-js@1.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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 CVE-2026-48069 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

A flaw was found in @grpc/grpc-js. An invalid incoming compressed message can cause a client or server process to crash. This affects all clients and servers that use @grpc/grpc-js. There is no workaround.

Workaround published by Red Hat
Upgrade to @grpc/grpc-js 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, or 1.14.4. There is no workaround for this vulnerability.
Source: Red Hat security advisory for CVE-2026-48069 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Developer Hub 1.10rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:1785332825RHSA-2026:48126
Red Hat Developer Hub 1.10rhdh/rhdh-hub-rhel9:1785411652RHSA-2026:49642
Red Hat Developer Hub 1.9rhdh/rhdh-hub-rhel9:1785972843RHSA-2026:52768

Frequently Asked Questions

@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 compressed message can cause a client or server process that uses @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.
O3 Security · Impact-Aware SCA

Is CVE-2026-48069 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-48069: @grpc/grpc-js — Fixed in 1.9.16